# CVE-2026-5271: pymanager included the current working directory in sys.path meaning modules could be shadowed by modules in the current working directory.

Source: https://junglewise.ai/threats/cve-2026-5271-pymanager-included-the-current-working-directory-in-sys-path  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-01  
License: CC BY 4.0 with a link back

CVE-2026-5271 · Severity: high · CVSS 7.8 · Published 2026-04-01

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.

Vendors: [Python](https://junglewise.ai/threats/vendors/python).

## Quick answers

**Is CVE-2026-5271 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-5271 being exploited in the wild.

**How severe is CVE-2026-5271?** High severity, with a CVSS score of 7.8, published 1 April 2026.

**Which products and versions are affected?** Python Pymanager. The advisory does not name versions.

**Is there a fix for CVE-2026-5271?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**Am I affected by CVE-2026-5271?** Check whether you run Python Pymanager. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Affected products

- Python Pymanager