Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2026-12003

Published Jun 16, 2026 CWE-427 EPSS 0.15% (4th pctl)

Overview

CVE-2026-12003 is a known-severity vulnerability. It was published on June 16, 2026.

Technical 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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently Asked Questions

What is CVE-2026-12003?

CVE-2026-12003 is a known-severity vulnerability. It was published on June 16, 2026.

How severe is CVE-2026-12003?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-12003?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-12003?

CyberStrike's AI-powered security agents can automatically detect CVE-2026-12003 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.