How severe is CVE-2026-8643?

No CVSS score has been assigned to CVE-2026-8643 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-8643?

CVE-2026-8643 affects the following packages: pip (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-8643?

Update pip to 26.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-8643 is resolved across your whole dependency graph.

How do I detect CVE-2026-8643 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pip, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-8643 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-8643 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-8643 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-8643?

CVE-2026-8643 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-8643?

CVE-2026-8643 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-8643 published, and has it been updated?

CVE-2026-8643 was published on June 1, 2026 and was last updated on October 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-8643 — pip

Fix: pypa/pip#14000

CVE-2026-8643 is a Path Traversal vulnerability in pip. A fix is available for pip — see the affected versions and patch details below.

pip can extract console_scripts and gui_scripts outside installation directory

Also known asGHSA-wf93-45jw-7689PYSEC-2026-196

Published

Jun 1, 2026

Updated

Oct 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 14, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-8643.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs39th percentile — riskier than 39% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍pip

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`pip`	all versions	26.1.2`pip install --upgrade 'pip==26.1.2'`

Affected Products

1 product · 1 configurations

Application

pippypa

< 26.1.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pip, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pip to 26.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-8643 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This Important flaw in pip's wheel installation process allows for arbitrary file overwrite due to path traversal. An attacker could exploit this by convincing a user to install a specially crafted malicious Python wheel. While file overwrites are limited to the installing user's permissions, using `pip install` with…

Workaround published by Red Hat

To mitigate this issue, users should avoid installing Python wheels from untrusted sources. It is strongly advised against using `pip install` with elevated privileges, such as `sudo`, when installing wheels. Additionally, administrators should inspect `entry_points.txt` within wheels for path separators or absolute paths before installation.

Source: Red Hat security advisory for CVE-2026-8643 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Ansible Automation Platform 2.5 for RHEL 8	`automation-controller-0:4.6.30-2.el8ap`	RHSA-2026:42078
Red Hat Ansible Automation Platform 2.6 for RHEL 9	`automation-controller-0:4.7.14-3.el9ap`	RHSA-2026:42079
Red Hat Enterprise Linux 10	`python3.14-pip-0:25.2-3.el10_2.5`	RHSA-2026:36193
Red Hat Enterprise Linux 9	`python3.14-pip-0:25.2-3.el9_8.5`	RHSA-2026:36315
Red Hat Ansible Automation Platform 2.5	`ansible-automation-platform-25/controller-rhel8:1784049109`	RHSA-2026:42144
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-26/de-minimal-rhel9:1782711769`	RHSA-2026:34374
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-tech-preview/metrics-service-rhel9:1783969139`	RHSA-2026:42132
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-26/controller-rhel9:1785753810`	RHSA-2026:50479

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-8643 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works