CVE-2026-5271

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data tampering.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-04-01 14:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-26 21:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.2% in the next 30 days (EPSS).
• Severity: 5.6 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-04-01 14:16 UTC

Last modified

2026-10-26 21:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-427

Record status

Analyzed

Affected

• Python Pymanager 26.0

Attack profile CVSS 4.0 · 5.6

Attack vector

Local

Complexity

Low

Attack requirements

Present

Privileges needed

None

User interaction

Active

Confidentiality

None

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-5271.md and follow it. Check whether this project is affected by CVE-2026-5271. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge