pymanager included the current working directory in sys.path meaning modules could be shadowed by modules in the current working directory. As a result, if a user executes a pymanager-generated command (e.g., pip, pytest) from an attacker-controlled directory, a malicious module in that directory can be imported and executed instead of the intended package.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/python/pymanager/security/advisories/GHSA-jr5x-hgm4-rrm6 Exploit, Vendor Advisory
- https://github.com/python/pymanager/security/advisories/GHSA-jr5x-hgm4-rrm6 Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.6 · pythonNVD modified 2026-10-26 21:10
Affected (CPE criteria) 1
cpe:2.3:a:python:pymanager:26.0:*:*:*:*:*:*:*
References 3
- https://github.com/python/pymanager/security/advisories/GHSA-jr5x-hgm4-rrm6 Exploit, Vendor Advisory
- http://www.openwall.com/lists/oss-security/2026/04/01/5 Mailing List, Third Party Advisory
- https://github.com/python/pymanager/security/advisories/GHSA-jr5x-hgm4-rrm6 Exploit, Vendor Advisory