{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-12003", "assignerOrgId": "28c92f92-d60d-412d-b760-e73465c3df22", "state": "PUBLISHED", "assignerShortName": "PSF", "dateReserved": "2026-06-11T17:05:37.519Z", "datePublished": "2026-06-16T15:18:42.998Z", "dateUpdated": "2026-06-16T19:12:36.706Z"}, "containers": {"cna": {"affected": [{"defaultStatus": "unaffected", "product": "CPython", "repo": "https://github.com/python/cpython", "vendor": "Python Software Foundation", "versions": [{"version": "0", "lessThan": "3.15.0", "status": "affected", "versionType": "python"}]}], "credits": [{"lang": "en", "type": "reporter", "value": "Jake Yamaki (https://github.com/b6938236)"}, {"lang": "en", "type": "coordinator", "value": "Steve Dower (https://github.com/zooba)"}], "descriptions": [{"lang": "en", "supportingMedia": [{"type": "text/html", "value": "To allow builds of Python to be run from an in-tree layout (rather than<br>an installed file layout), the VPATH variable is defined at build time<br>and used to locate certain landmarks - specifically,<br>Modules/setup.local. When this landmark is found relative to VPATH<br>relative to the executable, Python assumes it is running in a source<br>tree and generates a different default sys.path. This code remains in<br>release builds, so that release-ready builds can be built in-tree.<br><br>On Windows, since builds are written to 'PCbuild/', the value of<br>VPATH is set to '..\\..', which results in a landmark of<br>'..\\..\\Modules\\setup.local'. This path is outside the install directory<br>of Python, and may have different permissions, potentially allowing a<br>low-privilege user to create the landmark and an alternative `Lib`<br>folder that will be discovered by an otherwise restricted install.<br><br>Such a setup occurs with the legacy default install location for all<br>users (in the now superseded EXE installer), due to how Windows allows<br>all users to create folders in the root directory of their OS drive.<br><br>Our recommended mitigation on Windows is to migrate away from the<br>legacy installer and use the new [Python install<br>manager](https://www.python.org/downloads/latest/pymanager/) to install<br>for the current user. Installs where the directory two levels above the<br>Python installation directory have equivalent permissions are unaffected<br>(in general, a per-user install cannot be modified at all by other<br>users, removing any escalation of privilege risk, and could be directly<br>modified by a privileged user, making the potential tampering<br>irrelevant). Alternative mitigations might include preemptively creating<br>and restricting access to a `Modules` directory. Be aware that only 3.13<br>and 3.14 will receive updated legacy installers - earlier fixes are only<br>provided as sources.<br><br>Platforms other than Windows allow VPATH to be overridden, but as they<br>don't usually use a separated directory in the build for binaries, are<br>unlikely to have a landmark reference outside of the install directory.<br><br>The landmark detection involving VPATH is a fallback for when a more<br>specific landmark - .\\pybuilddir.txt - is absent, and was included for<br>compatibility. Future releases of Python will no longer include the<br>fallback, and so builds will need to generate or preserve the<br>pybuilddir.txt file in order to work in-tree. This landmark file has<br>been generated on Windows since 3.11, and on other platforms for longer."}], "value": "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."}], "metrics": [{"cvssV4_0": {"Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "Safety": "NOT_DEFINED", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "attackVector": "LOCAL", "baseScore": 5.3, "baseSeverity": "MEDIUM", "exploitMaturity": "NOT_DEFINED", "privilegesRequired": "LOW", "providerUrgency": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "userInteraction": "ACTIVE", "valueDensity": "NOT_DEFINED", "vectorString": "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", "vulnAvailabilityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "vulnerabilityResponseEffort": "NOT_DEFINED"}, "format": "CVSS", "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "problemTypes": [{"descriptions": [{"cweId": "CWE-427", "description": "CWE-427", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"orgId": "28c92f92-d60d-412d-b760-e73465c3df22", "shortName": "PSF", "dateUpdated": "2026-06-16T15:27:24.909Z"}, "references": [{"tags": ["patch"], "url": "https://github.com/python/cpython/pull/151545"}, {"tags": ["issue-tracking"], "url": "https://github.com/python/cpython/issues/151544"}, {"tags": ["vendor-advisory"], "url": "https://https://mail.python.org/archives/list/[email protected]/thread/JIFOBO7UX3LY4VJKJUOKYJV62CFR2IRH/"}], "source": {"discovery": "UNKNOWN"}, "title": "CPython >3.11 Insecure Input Validation resulting in privilege escalation", "x_generator": {"engine": "cvelib 1.8.0"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2026-06-16T17:53:54.916961Z", "id": "CVE-2026-12003", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-06-16T17:56:25.731Z"}}, {"title": "CVE Program Container", "references": [{"url": "http://www.openwall.com/lists/oss-security/2026/06/16/8"}], "providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2026-06-16T19:12:36.706Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-12003", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-06-16T17:53:54.916961Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-06-16T17:55:24.371Z"}}], "cna": {"title": "CPython >3.11 Insecure Input Validation resulting in privilege escalation", "source": {"discovery": "UNKNOWN"}, "credits": [{"lang": "en", "type": "reporter", "value": "Jake Yamaki (https://github.com/b6938236)"}, {"lang": "en", "type": "coordinator", "value": "Steve Dower (https://github.com/zooba)"}], "metrics": [{"format": "CVSS", "cvssV4_0": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 5.3, "Automatable": "NOT_DEFINED", "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "valueDensity": "NOT_DEFINED", "vectorString": "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", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "ACTIVE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "LOW", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "vulnerabilityResponseEffort": "NOT_DEFINED"}, "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "affected": [{"repo": "https://github.com/python/cpython", "vendor": "Python Software Foundation", "product": "CPython", "versions": [{"status": "affected", "version": "0", "lessThan": "3.15.0", "versionType": "python"}], "defaultStatus": "unaffected"}], "references": [{"url": "https://github.com/python/cpython/pull/151545", "tags": ["patch"]}, {"url": "https://github.com/python/cpython/issues/151544", "tags": ["issue-tracking"]}, {"url": "https://https://mail.python.org/archives/list/[email protected]/thread/JIFOBO7UX3LY4VJKJUOKYJV62CFR2IRH/", "tags": ["vendor-advisory"]}], "x_generator": {"engine": "cvelib 1.8.0"}, "descriptions": [{"lang": "en", "value": "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.", "supportingMedia": [{"type": "text/html", "value": "To allow builds of Python to be run from an in-tree layout (rather than<br>an installed file layout), the VPATH variable is defined at build time<br>and used to locate certain landmarks - specifically,<br>Modules/setup.local. When this landmark is found relative to VPATH<br>relative to the executable, Python assumes it is running in a source<br>tree and generates a different default sys.path. This code remains in<br>release builds, so that release-ready builds can be built in-tree.<br><br>On Windows, since builds are written to 'PCbuild/', the value of<br>VPATH is set to '..\\..', which results in a landmark of<br>'..\\..\\Modules\\setup.local'. This path is outside the install directory<br>of Python, and may have different permissions, potentially allowing a<br>low-privilege user to create the landmark and an alternative `Lib`<br>folder that will be discovered by an otherwise restricted install.<br><br>Such a setup occurs with the legacy default install location for all<br>users (in the now superseded EXE installer), due to how Windows allows<br>all users to create folders in the root directory of their OS drive.<br><br>Our recommended mitigation on Windows is to migrate away from the<br>legacy installer and use the new [Python install<br>manager](https://www.python.org/downloads/latest/pymanager/) to install<br>for the current user. Installs where the directory two levels above the<br>Python installation directory have equivalent permissions are unaffected<br>(in general, a per-user install cannot be modified at all by other<br>users, removing any escalation of privilege risk, and could be directly<br>modified by a privileged user, making the potential tampering<br>irrelevant). Alternative mitigations might include preemptively creating<br>and restricting access to a `Modules` directory. Be aware that only 3.13<br>and 3.14 will receive updated legacy installers - earlier fixes are only<br>provided as sources.<br><br>Platforms other than Windows allow VPATH to be overridden, but as they<br>don't usually use a separated directory in the build for binaries, are<br>unlikely to have a landmark reference outside of the install directory.<br><br>The landmark detection involving VPATH is a fallback for when a more<br>specific landmark - .\\pybuilddir.txt - is absent, and was included for<br>compatibility. Future releases of Python will no longer include the<br>fallback, and so builds will need to generate or preserve the<br>pybuilddir.txt file in order to work in-tree. This landmark file has<br>been generated on Windows since 3.11, and on other platforms for longer."}]}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-427", "description": "CWE-427"}]}], "providerMetadata": {"orgId": "28c92f92-d60d-412d-b760-e73465c3df22", "shortName": "PSF", "dateUpdated": "2026-06-16T15:27:24.909Z"}}}, "cveMetadata": {"cveId": "CVE-2026-12003", "state": "PUBLISHED", "dateUpdated": "2026-06-16T17:56:25.731Z", "dateReserved": "2026-06-11T17:05:37.519Z", "assignerOrgId": "28c92f92-d60d-412d-b760-e73465c3df22", "datePublished": "2026-06-16T15:18:42.998Z", "assignerShortName": "PSF"}, "dataVersion": "5.2"}

{"cveTags": [], "descriptions": [{"lang": "en", "value": "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."}], "id": "CVE-2026-12003", "lastModified": "2026-06-16T17:37:16.933", "metrics": {"cvssMetricV40": [{"cvssData": {"Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "Safety": "NOT_DEFINED", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "attackVector": "LOCAL", "availabilityRequirement": "NOT_DEFINED", "baseScore": 5.3, "baseSeverity": "MEDIUM", "confidentialityRequirement": "NOT_DEFINED", "exploitMaturity": "NOT_DEFINED", "integrityRequirement": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "privilegesRequired": "LOW", "providerUrgency": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "userInteraction": "ACTIVE", "valueDensity": "NOT_DEFINED", "vectorString": "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", "version": "4.0", "vulnAvailabilityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "vulnerabilityResponseEffort": "NOT_DEFINED"}, "source": "[email protected]", "type": "Secondary"}]}, "published": "2026-06-16T17:16:31.667", "references": [{"source": "[email protected]", "url": "https://github.com/python/cpython/issues/151544"}, {"source": "[email protected]", "url": "https://github.com/python/cpython/pull/151545"}, {"source": "[email protected]", "url": "https://https://mail.python.org/archives/list/[email protected]/thread/JIFOBO7UX3LY4VJKJUOKYJV62CFR2IRH/"}], "sourceIdentifier": "[email protected]", "vulnStatus": "Awaiting Analysis", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-427"}], "source": "[email protected]", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[0,3.15.0)"}}], "enrichment": {"confidence": 95.0, "confidence_source": "inferred", "scores": [{"score": 95.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "CPython", "source": "cna", "vendor": "Python Software Foundation"}, "product": "cpython", "vendor": "python"}], "created": "2026-06-16T18:00:05.765912+00:00", "updated": "2026-06-16T18:00:05.765945+00:00", "vendors": ["python", "python$PRODUCT$cpython"]}