ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-5271

pymanager included the current working directory in sys.path meaning modules could be shadowed by modules in the current working directory.

Published Apr 1, 2026 · catalog updated Jun 17, 2026 · pymanager included the current

Check if you run it

No confirmed exploitation is on record for CVE-2026-5271. EPSS is 0.19%. Act only if a listed version of pymanager included the current is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (pymanager included the current).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.6
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.19%
Remediation
Advisory link
Affected products
cpe python/pymanager

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe python/pymanager26.0

How to fix CVE-2026-5271

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-5271. EPSS is 0.19%. Act only if a listed version of pymanager included the current is installed.

Which versions are affected?

Compare what you have installed with 26.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-427: Uncontrolled Search Path Element. EPSS 0.19%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Apr 1, 2026 · NIST NVD

    Detected

    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.

  2. Jun 17, 2026 · NIST NVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2026-5271

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-5271

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDVulnerability recordCVE-2026-5271

    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

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.