GHSA-5xjx-3w67-w9x9

pypi-publish action revocation of CA in the chain that Sigstore uses in Trusted Publishing and Digital Attestations for PyPI

Critical highest severity reported

4
catalog tools match this advisory
0
ship the vulnerable code in their release binary (Go tools analyzed with govulncheck)
No
in the CISA KEV catalog

Every match is a GitHub Action referenced in a workflow file, not a dependency of the shipped tool.

Catalog tools matching GHSA-5xjx-3w67-w9x9

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
in-toto
Supply Chain Compliance
v3.1.0pypa/gh-action-pypi-publish@v1.14.0
github
1.14.3not analyzed.github/workflows/cd.yml (workflow)Dispute
prowler
Cloud Security
5.47.0pypa/gh-action-pypi-publish@v1.14.2
github
1.14.3not analyzed.github/workflows/mcp-pypi-release.yml (workflow)Dispute
cloudsplaining
Cloud Security
0.9.1pypa/gh-action-pypi-publish@v1.13.0
github
1.14.3not analyzed.github/workflows/publish.yml (workflow)Dispute
detect-secrets
Pre-commit & Secrets Detection
v1.5.0pypa/gh-action-pypi-publish@v1.5.0
github
1.14.3not analyzed.github/workflows/pypi.yml (workflow)Dispute

Vulnerabilities are known advisories that Grype matches against the dependencies declared in each project's release source (manifests and lockfiles, including development and build dependencies). A match does not mean the tool is exploitable: the vulnerable code may be unused, test-only, or not shipped in the released binary. KEV: listed in the CISA Known Exploited Vulnerabilities catalog. EPSS: FIRST's estimated probability of exploitation in the next 30 days. Both describe the vulnerability in general, not its exploitability through this tool; a match in a workflow file refers to a GitHub Action, not to shipped code. Released binary is only analyzed for Go tools with a Linux release binary; other tools show not analyzed.

Advisory sources

GitHub advisory GHSA-5xjx-3w67-w9x9 · OSV GHSA-5xjx-3w67-w9x9

Grype data sources: https://github.com/advisories/GHSA-5xjx-3w67-w9x9