CVE-2026-5271: Possible to hijack modules in current working directory
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-5271?
The severity of CVE-2026-5271 is classified as high due to the risk of module hijacking.
How do I fix CVE-2026-5271?
To fix CVE-2026-5271, you should modify the sys.path to exclude the current working directory or upgrade to a patched version of pymanager.
What are the potential impacts of CVE-2026-5271?
The potential impacts of CVE-2026-5271 include the execution of malicious modules and disruption of applications relying on the pymanager library.
Which software is affected by CVE-2026-5271?
The affected software for CVE-2026-5271 is the pymanager library available on PyPI.
Is CVE-2026-5271 a critical vulnerability?
Yes, CVE-2026-5271 is considered a critical vulnerability due to its ability to compromise the integrity of Python applications.