CVE-2026-12003CPython >3.11 Insecure Input Validation resulting in privilege escalation
- 5.3MediumCVSS base score
- 0.14%Exploitation in 30 daysEPSS · top 96% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By PSF
- 5 days later
· 5 days later
Published
- 58 days later
· 58 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| PSFCNA (assigner) | 4.0 | Medium5.3 | CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N |
| NVDNVD · Awaiting Analysis | 4.0 | Medium5.3 | CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
- EPSS (exploitation in 30 days)
- 0.14% · top 96% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.3.
Affected products
Python Software Foundation · CPython
- affected < 3.11.16
- affected 3.12.0 – < 3.12.14
- affected 3.13.0 – < 3.13.15
- affected 3.14.0 – < 3.14.7
- affected 3.15.0a1 – < 3.15.0b3
References
References10
- https://github.com/python/cpython/pull/151545 (opens in a new tab)patch
- https://github.com/python/cpython/issues/151544 (opens in a new tab)issue-tracking
- https://https://mail.python.org/archives/list/[email protected]/thread/JIFOBO7UX3LY4VJKJUOKYJV62CFR2IRH/ (opens in a new tab)vendor-advisory
- https://github.com/python/cpython/commit/16c40f944b7bff724a403cf4902763d095bb4b2a (opens in a new tab)patch
- https://github.com/python/cpython/commit/9e863fab283eddca9c2a8f9d1ee30f4dc243e314 (opens in a new tab)patch
- https://github.com/python/cpython/commit/a86de0bc236fbb9452f98998fc8437e9fca35700 (opens in a new tab)patch
- https://github.com/python/cpython/commit/b93d6d3399adbd3a5037b6b92fc3587c85ac5d56 (opens in a new tab)patch
- https://github.com/python/cpython/commit/03ab7b44788bfd6b8927e16bcdbd025aa08dce06 (opens in a new tab)patch
- https://github.com/python/cpython/commit/872038377db2e170e0e140b5f8aaedf636b3fbf5 (opens in a new tab)patch
- http://www.openwall.com/lists/oss-security/2026/06/16/8 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-37125 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-12003)Record last updated .