Microsoft · Virtual environment (venv) activation scripts don't quote paths
Affects MicrosoftSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 08:59 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Exploitation evidence
Disclosed: evidence found.
CVE published 8 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Security Response Center Microsoft | Affected
| Fixed in– |
AI-suggested
Until a fix is available, users should be cautious with virtual environment activation scripts, especially in environments where path names contain spaces or special characters.
Description
The vulnerability CVE-2024-9287 involves virtual environment (venv) activation scripts that do not properly quote paths. This issue can potentially cause problems when paths contain spaces or special characters, leading to incorrect script execution or security risks related to path interpretation.