GHSA-xmj3-9gf7-h52w

setuptools: Windows path escape via namespace_packages.txt during legacy wheel installation Description

Low highest severity reported

5
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

Catalog tools matching GHSA-xmj3-9gf7-h52w

ToolVersion scannedPackageFixed inReleased binaryDeclared in or found inDispute
cloudquery
Cloud Security
cli-v6.49.2setuptools@82.0.1
pypi
84.1.0not analyzedplugins/source/square/uv.lockDispute
KubeStellar Console
Kubernetes Security
v0.3.42setuptools@84.0.0
pypi
84.1.0not analyzed.github/requirements-nightly.txtDispute
cartography
Cloud Security
0.144.0setuptools@80.10.2
pypi
84.1.0not analyzeduv.lockDispute
prowler
Cloud Security
5.47.0setuptools@80.10.2
pypi
84.1.0not analyzedapi/uv.lockDispute
prowler
Cloud Security
5.47.0setuptools@82.0.1
pypi
84.1.0not analyzeduv.lockDispute
semgrep
Static Application Security Testing (SAST) › Multi-language
v1.183.0setuptools@80.10.2
pypi
84.1.0not analyzedcli/uv.lockDispute

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-xmj3-9gf7-h52w · OSV GHSA-xmj3-9gf7-h52w

Grype data sources: https://github.com/advisories/GHSA-xmj3-9gf7-h52w