Skip to main content
VulnerabilityPublished Updated

CVE-2024-9287: Python Software Foundation CPython · Unquoted Search Path or Element

Affects Python Software Foundation CPythonSource GCVE Database

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 02:27 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (PSF)CVSS 4.05.3
CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/U:Green

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Python Software Foundation CPythonAffected
  • 0 – 3.14.0a1
6 affected builds
Fixed in–

AI-suggested

Users should avoid activating virtual environments created by untrusted sources. Using the Python interpreter directly from the virtual environment without activating it (e.g., './venv/bin/python') avoids the risk. Monitor the Python Software Foundation advisories for updates and patches addressing this issue.

Description

CVE-2024-9287 is a medium severity vulnerability in the Python Software Foundation's CPython implementation affecting the venv module and CLI. It arises from unquoted path names when creating virtual environments, allowing attacker-controlled virtual environments to inject commands into activation scripts. This can lead to execution of arbitrary commands when the virtual environment is activated using 'source venv/bin/activate'. Virtual environments not created by an attacker or those used without activation (e.g., running './venv/bin/python' directly) are not affected.

References

Community reviews

Loading reviews…