# CVE-2026-12003: CPython >3.11 Insecure Input Validation resulting in privilege escalation > Low-privilege users can escalate privileges by creating specific files in the parent directory of a legacy Windows Python installation, altering the module search path. - **Severity:** Medium 5.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`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 16 Jun 2026 - **Updated:** 13 Aug 2026 - **Also known as:** AZL-90182, BIT-libpython-2026-12003, BIT-python-2026-12003, BIT-python-min-2026-12003, DEBIAN-CVE-2026-12003, ECHO-d378-1b5a-f13e, GHSA-2wqx-fp26-qh5v, MINI-2c3j-7mc6-xmmv, MINI-47ph-86jv-r2mh, MINI-977f-5rv2-cr5m, MINI-hhw7-p579-3x6g, MINI-p5xr-6254-xxx9, PSF-2026-28, UBUNTU-CVE-2026-12003 ## What is CVE-2026-12003? CVE-2026-12003 is a medium-severity vulnerability in CPython, published on 16 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official 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. Weakness: CWE-427 (Uncontrolled Search Path Element) ## Which versions are affected by CVE-2026-12003? 3 open source packages ship an affected version, including libpython, python and python-min. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libpython` | Bitnami | All versions | 3.11.16, 3.12.14, 3.13.15, 3.14.7 | | `python` | Bitnami | All versions | 3.11.16, 3.12.14, 3.13.15, 3.14.7 | | `python-min` | Bitnami | All versions | 3.11.16, 3.12.14, 3.13.15, 3.14.7 | ## How do I fix CVE-2026-12003? Upgrade libpython to a fixed version for your release line: 3.11.16, 3.12.14, 3.13.15 or 3.14.7. ## Is CVE-2026-12003 being exploited? There is no known exploitation of CVE-2026-12003 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-12003 and fix it if it is affected. What it is: CVE-2026-12003 is a medium-severity vulnerability in CPython, published on 16 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-12003 in the wild and no public exploit code. Affected packages and fixed versions: - libpython (Bitnami): affected all versions; fixed in 3.11.16, 3.12.14, 3.13.15, 3.14.7 - python (Bitnami): affected all versions; fixed in 3.11.16, 3.12.14, 3.13.15, 3.14.7 - python-min (Bitnami): affected all versions; fixed in 3.11.16, 3.12.14, 3.13.15, 3.14.7 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-12003/ (Markdown: https://insights.sbomify.com/CVE-2026-12003/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-12003 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-12003 - OSV: https://osv.dev/vulnerability/CVE-2026-12003 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-12003/ Summaries are generated and may contain mistakes; the official description above is the record.