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

Routine

HIGH 7.8DOWNGRADE

CVE-2026-5271 is a high-severity flaw (CVSS 7.8) affecting pymanager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.8 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 93%)
CISA exploited list	No
Weakness	CWE-427
Published	2026-04-01
Last modified	2026-10-26

Publisher (CNA): Python Software Foundation · Vendor: python

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-01 14:16 UTCPublished CVE record published
2026-10-26 21:10 UTCUpdated Record last modified

python pymanager DOWNGRADE

Affected: 26.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 26.0

1. Check installed version

apt-cache policy pymanager || rpm -q pymanager || pymanager --version

2. No fixed release: DOWNGRADE to a release before 26.0 (Debian / Ubuntu)

apt-cache madison pymanager sudo apt install pymanager=<VERSION_BEFORE_26.0> sudo apt-mark hold pymanager

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list pymanager sudo dnf downgrade pymanager-<VERSION_BEFORE_26.0> sudo dnf versionlock add pymanager

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-5271?

pymanager: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-5271 being exploited?

CVE-2026-5271 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-5271 affect?

CVE-2026-5271 affects pymanager. Severity is high (CVSS 7.8). 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-

How urgent is CVE-2026-5271?

Priority 34/100. High severity; Public exploit reference

Software pages

Python vulnerabilities

References

← Back to latest CVEs