CVE-2026-12003
Last modified
CVE-2026-12003 is a medium-severity vulnerability rated 5.3/10 on the CVSS scale. To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the VPATH variable is defined at build time and used to locate certain landmarks - specifically, Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python assumes it is running in a source tree and generates a different default sys.path. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
Description
To allow builds of Python to be run from an in-tree layout (rather than an installed file layout), the VPATH variable is defined at build time and used to locate certain landmarks - specifically, Modules/setup.local. When this landmark is found relative to VPATH relative to the executable, Python assumes it is running in a source tree and generates a different default sys.path. This code remains in release builds, so that release-ready builds can be built in-tree. On Windows, since builds are written to 'PCbuild/', the value of VPATH is set to '..\..', which results in a landmark of '..\..\Modules\setup.local'. This path is outside the install directory of Python, and may have different permissions, potentially allowing a low-privilege user to create the landmark and an alternative `Lib` folder that will be discovered by an otherwise restricted install. Such a setup occurs with the legacy default install location for all users (in the now superseded EXE installer), due to how Windows allows all users to create folders in the root directory of their OS drive. Our recommended mitigation on Windows is to migrate away from the legacy installer and use the new [Python install manager](https://www.python.org/downloads/latest/pymanager/) to install for the current user. Installs where the directory two levels above the Python installation directory have equivalent permissions are unaffected (in general, a per-user install cannot be modified at all by other users, removing any escalation of privilege risk, and could be directly modified by a privileged user, making the potential tampering irrelevant). Alternative mitigations might include preemptively creating and restricting access to a `Modules` directory. Be aware that only 3.13 and 3.14 will receive updated legacy installers - earlier fixes are only provided as sources. Platforms other than Windows allow VPATH to be overridden, but as they don't usually use a separated directory in the build for binaries, are unlikely to have a landmark reference outside of the install directory. The landmark detection involving VPATH is a fallback for when a more specific landmark - .\pybuilddir.txt - is absent, and was included for compatibility. Future releases of Python will no longer include the fallback, and so builds will need to generate or preserve the pybuilddir.txt file in order to work in-tree. This landmark file has been generated on Windows since 3.11, and on other platforms for longer.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Python Software Foundation | CPython | < 3.11.16; >= 3.12.0, < 3.12.14; >= 3.13.0, < 3.13.15; >= 3.14.0, < 3.14.7; >= 3.15.0a1, < 3.15.0b3 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-12003?
How severe is CVE-2026-12003?
How do I fix CVE-2026-12003?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-120014SAP HANA XSA Web Dispatcher does not perform sufficient requ…7.6
- CVE-2026-120015SAP Host Agent does not sufficiently validate certain inputs…7.5
- CVE-2026-120016SAP NetWeaver Visual Composer does not perform sufficient in…6.1
- CVE-2026-120017SAP NetWeaver AS ABAP and ABAP Platform does not perform suf…10
- CVE-2026-120019The W3 Total Cache plugin for WordPress is vulnerable to Sto…5.4
- CVE-2026-12002The Smash Balloon Social Photo Feed – Easy Social Feeds Plug…4.7
- CVE-2026-120033In FRRouting, bgpd does not correctly close a BGP session wh…6
- CVE-2026-120035The RSS Aggregator by Feedzy – Feed to Post, Autoblogging, N…5.4
- CVE-2026-12004IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Ver…8.7
- CVE-2026-120040The Mail logging & Catcher plugin for WordPress is vulnerabl…7.5
- CVE-2026-120043The Affiliate Program Suite — SliceWP Affiliates plugin for …7.5
- CVE-2026-120046Nezha 2.0.0 before 2.4.0 contains a NULL pointer dereference…5.3
Are you affected by CVE-2026-12003?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
