{"answers":{"affected":"3 open source packages ship an affected version, including libpython, python and python-min.","exploited":"There is no known exploitation of CVE-2026-12003 in the wild and no public exploit code.","fix":"Upgrade libpython to a fixed version for your release line: 3.11.16, 3.12.14, 3.13.15 or 3.14.7.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-12003 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-12003 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- libpython (Bitnami): affected all versions; fixed in 3.11.16, 3.12.14, 3.13.15, 3.14.7\n- python (Bitnami): affected all versions; fixed in 3.11.16, 3.12.14, 3.13.15, 3.14.7\n- python-min (Bitnami): affected all versions; fixed in 3.11.16, 3.12.14, 3.13.15, 3.14.7\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-12003/ (Markdown: https://insights.sbomify.com/CVE-2026-12003/index.md)","id":"CVE-2026-12003","markdown":"https://insights.sbomify.com/CVE-2026-12003/index.md","name":"CVE-2026-12003","record":{"aliases":["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"],"analysis":{"component_type":"library","fix_type":"configuration_change","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Python interpreter","requires_auth":"low_privilege","summary":"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.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"PSF","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"To allow builds of Python to be run from an in-tree layout (rather than\nan installed file layout), the VPATH variable is defined at build time\nand used to locate certain landmarks - specifically,\nModules/setup.local. When this landmark is found relative to VPATH\nrelative to the executable, Python assumes it is running in a source\ntree and generates a different default sys.path. This code remains in\nrelease builds, so that release-ready builds can be built in-tree.\n\nOn Windows, since builds are written to 'PCbuild/', the value of\nVPATH is set to '..\\..', which results in a landmark of\n'..\\..\\Modules\\setup.local'. This path is outside the install directory\nof Python, and may have different permissions, potentially allowing a\nlow-privilege user to create the landmark and an alternative `Lib`\nfolder that will be discovered by an otherwise restricted install.\n\nSuch a setup occurs with the legacy default install location for all\nusers (in the now superseded EXE installer), due to how Windows allows\nall users to create folders in the root directory of their OS drive.\n\nOur recommended mitigation on Windows is to migrate away from the\nlegacy installer and use the new [Python install\nmanager](https://www.python.org/downloads/latest/pymanager/) to install\nfor the current user. Installs where the directory two levels above the\nPython installation directory have equivalent permissions are unaffected\n(in general, a per-user install cannot be modified at all by other\nusers, removing any escalation of privilege risk, and could be directly\nmodified by a privileged user, making the potential tampering\nirrelevant). Alternative mitigations might include preemptively creating\nand restricting access to a `Modules` directory. Be aware that only 3.13\nand 3.14 will receive updated legacy installers - earlier fixes are only\nprovided as sources.\n\nPlatforms other than Windows allow VPATH to be overridden, but as they\ndon't usually use a separated directory in the build for binaries, are\nunlikely to have a landmark reference outside of the install directory.\n\nThe landmark detection involving VPATH is a fallback for when a more\nspecific landmark - .\\pybuilddir.txt - is absent, and was included for\ncompatibility. Future releases of Python will no longer include the\nfallback, and so builds will need to generate or preserve the\npybuilddir.txt file in order to work in-tree. This landmark file has\nbeen generated on Windows since 3.11, and on other platforms for longer.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"CPython \u003e3.11 Insecure Input Validation resulting in privilege escalation","id":"CVE-2026-12003","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":3,"n_references":9,"next":{"headline":"Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-12004"},"packages":[{"ecosystem":"Bitnami","fixed":["3.11.16","3.12.14","3.13.15","3.14.7"],"introduced":["0","3.12.0","3.13.0","3.14.0"],"last_affected":[],"package":"libpython","purl":"pkg:bitnami/libpython","source":"BIT-libpython-2026-12003"},{"ecosystem":"Bitnami","fixed":["3.11.16","3.12.14","3.13.15","3.14.7"],"introduced":["0","3.12.0","3.13.0","3.14.0"],"last_affected":[],"package":"python","purl":"pkg:bitnami/python","source":"BIT-python-2026-12003"},{"ecosystem":"Bitnami","fixed":["3.11.16","3.12.14","3.13.15","3.14.7"],"introduced":["0","3.12.0","3.13.0","3.14.0"],"last_affected":[],"package":"python-min","purl":"pkg:bitnami/python-min","source":"BIT-python-min-2026-12003"}],"prev":{"headline":"Cross-site request forgery in Smash Balloon Social Photo Feed – Easy Social Feeds Plugin","id":"CVE-2026-12002"},"products":["CPython"],"published":"2026-06-16","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-13","vendors":["Python Software Foundation"]},"summary":"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.","url":"https://insights.sbomify.com/CVE-2026-12003/"}