Skip to content
Fencer Intel
medium —

GHSA-jqh4-m4qc-6f23 json

CI/CD pipeline vulnerabilities in GitHub Actions workflows

published 7mo ago modified 7mo ago

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository keras-team/keras. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Security advisory published by the maintainers of keras-team/keras for workflow-files: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.

Is GHSA-jqh4-m4qc-6f23 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of keras-team/keras published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.