setuptools vulnerabilities
Most extensible Python build backend with support for C/C++ extension modules
- Registry
- PyPI
- Latest
- 84.2.1
- License
- MIT
6 known advisories
The latest version, 84.2.1, is not affected by any of them. Projects on older versions may be.
pip install 'setuptools>=84.2.1'Is your project on an affected setuptools?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for setuptools
setuptools: Windows path escape via namespace_packages.txt during legacy wheel installation Description
- Affected
- >=38.2.2 <84.1.0
- Fixed in
- 84.1.0
setuptools: MANIFEST.in exclusion bypass in sdist via Unicode normalization collision (NFC/NFD) on macOS APFS/HFS+
- Affected
- <83.0.0
- Fixed in
- 83.0.0
setuptools has a path traversal vulnerability in PackageIndex.download that leads to Arbitrary File Write
- Affected
- <78.1.1
- Fixed in
- 78.1.1
setuptools vulnerable to Command Injection via package URL
- Affected
- <70.0.0
- Fixed in
- 70.0.0
pypa/setuptools vulnerable to Regular Expression Denial of Service (ReDoS)
- Affected
- <65.5.1
- Fixed in
- 65.5.1
Setuptools vulnerable to Man-in-the-middle attacks
- Affected
- <0.7
- Fixed in
- 0.7
Is your setuptools version vulnerable?
Which of your client projects still run an old setuptools?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.