CPython Windows VPATH Landmark Search Path Privilege Escalation
CVE-2026-12003 is a moderate-severity vulnerability in CPython affecting versions up to and including 3.11.15, 3.12.13, 3.13.14, 3.14.6, and 3.15.0b2. CPython retains logic in release builds to support running from an in-tree build layout rather than an installed layout. That logic uses the build-time VPATH variable to locate landmarks such as Modules/setup.local; when such a landmark is found relative to the executable, Python assumes it is running from a source tree and generates an alternate default sys.path. On Windows, builds under PCbuild/<arch> set VPATH to ...., producing a landmark path of ....\Modules\setup.local. Because this path can resolve outside the Python installation directory, an attacker with low privileges may be able to create the expected landmark and a malicious alternative Lib directory in a location discovered by Python. This can cause an otherwise restricted Python installation to resolve imports from attacker-controlled locations.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
9 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.