CVE-2026-12003
published 2026-06-16CVE-2026-12003: 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…
PriorityP426medium5.3CVSS 4.0
AVLACLATPPRLUIAVCHVIHVANSCNSINSANEXCRXIRXARXMAVXMACXMATXMPRXMUIXMVCXMVIXMVAXMSCXMSIXMSAXSXAUXRXVXREXUX
EPSS
0.14%
3.5th percentile
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
unlike
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| python_software_foundation | cpython | < 3.15.0b3 | 3.15.0b3 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
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, Modu
ghsa_unreviewed·2026-06-16
CVE-2026-12003 [MEDIUM] CWE-427 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, Modu
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`
VulDB
Python CPython up to 3.14.x on Windows Installation Directory Modules/setup.local VPATH uncontrolled search path (ID 151544)
vuldb·2026-06-16·CVSS 5.3
CVE-2026-12003 [MEDIUM] Python CPython up to 3.14.x on Windows Installation Directory Modules/setup.local VPATH uncontrolled search path (ID 151544)
A vulnerability, which was classified as problematic, was found in Python CPython up to 3.14.x on Windows. This vulnerability affects unknown code of the file Modules/setup.local of the component Installation Directory Handler. The manipulation of the argument VPATH results in uncontrolled search path.
This vulnerability is reported as CVE-2026-12003. The attack requires a local approach. No exploit exists.
You should upgrade the affected component.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/python/cpython/commit/16c40f944b7bff724a403cf4902763d095bb4b2ahttps://github.com/python/cpython/commit/9e863fab283eddca9c2a8f9d1ee30f4dc243e314https://github.com/python/cpython/commit/a86de0bc236fbb9452f98998fc8437e9fca35700https://github.com/python/cpython/commit/b93d6d3399adbd3a5037b6b92fc3587c85ac5d56https://github.com/python/cpython/issues/151544https://github.com/python/cpython/pull/151545https://https://mail.python.org/archives/list/[email protected]/thread/JIFOBO7UX3LY4VJKJUOKYJV62CFR2IRH/http://www.openwall.com/lists/oss-security/2026/06/16/8
2026-06-16
Published