CVE-2026-8643: pip can extract console_scripts and gui_scripts outside installation directory
pip would treat console_scripts and gui_scripts as paths instead of file names without sanitizing the resolved absolute path to the installation directory, leading to entry points being installed outside the installation directory.
Security readout for executives and security teams
Plain-English summary
CVE-2026-8643 is a high-severity pip flaw where crafted package entry-point script names could be installed outside the intended installation directory. This matters most where developers, CI systems, or automation install Python packages from untrusted or compromised sources.
Executive priority
Treat as high priority for engineering and build environments because compromise of package installation workflows can affect code integrity and developer systems. No source in the bundle confirms active exploitation.
Technical view
pip 24.0 improperly treated console_scripts and gui_scripts as paths rather than sanitized filenames. The CVE maps to CWE-22 and carries CVSS 3.1 score 8.0 with user interaction and low privileges required. Source evidence identifies pip 24.0 and vendor/distribution advisories, but no active exploitation evidence is provided.
Likely exposure
Exposure is most likely on developer workstations, CI runners, build containers, and servers using pip 24.0 to install Python packages, especially from public indexes or less-controlled internal feeds.
Exploitation context
The bundle does not show KEV listing or confirmed active exploitation. Risk depends on a vulnerable pip 24.0 installation processing a malicious or compromised package with crafted entry points.
Researcher notes
Focus analysis on pip entry-point generation for console_scripts and gui_scripts and path containment around installation directories. Evidence is limited to the CVE record, PyPA patch reference, Python advisory, and Red Hat advisories.
Mitigation direction
Inventory systems and build images for pip 24.0.
Apply patched pip or distribution updates from official vendor guidance.
Prioritize CI, developer endpoints, and package-build infrastructure.
Restrict package installation to trusted sources until patched.
Review Red Hat advisories where Red Hat packages are used.
Validation and detection
Confirm pip 24.0 is absent from active runtimes and build images.
Check vendor package changelogs or advisories for CVE-2026-8643 coverage.
Verify CI runners and container bases were rebuilt after updates.
Review dependency sources for untrusted or unexpected package indexes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.