CVE-2026-8643: pip can extract console_scripts and gui_scripts outside installation directory
Noroxi assessment
Priority: Monitor (action score 16/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No special conditions are required; it is repeatable.
- Fixed version: Python Packaging Authority pip 26.1.2; azl3 python-pip 24.2-8 on Azure Linux 3.0 24.2-9; azl3 python-pip 24.2-9 on Azure Linux 3.0 24.2-9.
Low priority for now. Upgrade to Python Packaging Authority pip 26.1.2; azl3 python-pip 24.2-8 on Azure Linux 3.0 24.2-9; azl3 python-pip 24.2-9 on Azure Linux 3.0 24.2-9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- BDU:2026-10841
- GHSA-wf93-45jw-7689
- ALSA-2026:36193
- ALSA-2026:36315
- openSUSE-SU-2026:10940-1
- openSUSE-SU-2026:20993-1
- PYSEC-2026-196
- RHSA-2026:34891
- RHSA-2026:36193
- RHSA-2026:36315
- RHSA-2026:36359
- RHSA-2026:42079
- RLSA-2026:36193
- RLSA-2026:36315
- SUSE-SU-2026:22300-1
- SUSE-SU-2026:2634-1
- SUSE-SU-2026:3601-1
- SUSE-SU-2026:3635-1
- SUSE-SU-2026:3855-1
- SUSE-SU-2026:3862-1
- Published
- Jun 1, 2026
- Updated
- Sep 16, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- CWE-22
Report tools
Action score
16
Monitor
Low priority for now.
- CVSS
- 16 / 40 · 4.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · PSF
- 4.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pypa | pip | cpe:2.3:a:pypa:pip |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- pypa pipbefore 26.1.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (PSF). Independent of NVD's CPE analysis and usually ahead of it.
Python Packaging Authority pip
- 24.0 and later · before 26.1.2affected · python
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | python3.14-pip | before 25.2-3.el10_2.5 | 25.2-3.el10_2.5 |
| AlmaLinux:10 | python3.14-pip-wheel | before 25.2-3.el10_2.5 | 25.2-3.el10_2.5 |
| AlmaLinux:9 | python3.14-pip | before 25.2-3.el9_8.5 | 25.2-3.el9_8.5 |
| AlmaLinux:9 | python3.14-pip-wheel | before 25.2-3.el9_8.5 | 25.2-3.el9_8.5 |
| Debian:12 | python-pip | from 0 | — |
| Debian:14 | python-pip | before 26.1.2+dfsg-1 | 26.1.2+dfsg-1 |
| openSUSE:Leap 16.0 | python-pip | before 25.0.1-160000.5.1 | 25.0.1-160000.5.1 |
| openSUSE:Tumbleweed | python-pip | before 26.1.2-1.1 | 26.1.2-1.1 |
| PyPI | pip | before 26.1.2 | 26.1.2 |
| Red Hat:ansible_automation_platform_developer:2.6::el10 | ansible-core | before 2:2.16.19-1.el10ap | 2:2.16.19-1.el10ap |
| Red Hat:ansible_automation_platform_developer:2.6::el9 | ansible-core | before 1:2.16.19-1.el9ap | 1:2.16.19-1.el9ap |
| Red Hat:ansible_automation_platform_developer:2.6::el9 | receptor | before 0:1.6.6-1.el9ap | 0:1.6.6-1.el9ap |
| Red Hat:ansible_automation_platform:2.6::el10 | receptor | before 0:1.6.6-1.el10ap | 0:1.6.6-1.el10ap |
| Red Hat:ansible_automation_platform:2.6::el9 | automation-controller-venv-tower | before 0:4.7.14-3.el9ap | 0:4.7.14-3.el9ap |
| Red Hat:ansible_automation_platform:2.6::el9 | automation-gateway-proxy | before 0:2.6.17-1.el9ap | 0:2.6.17-1.el9ap |
| Red Hat:ansible_automation_platform:2.6::el9 | automation-gateway-proxy-debugsource | before 0:2.6.17-1.el9ap | 0:2.6.17-1.el9ap |
| Red Hat:ansible_automation_platform:2.6::el9 | automation-gateway-proxy-server | before 0:2.6.17-1.el9ap | 0:2.6.17-1.el9ap |
| Red Hat:ansible_automation_platform:2.6::el9 | automation-gateway-proxy-server-debuginfo | before 0:2.6.17-1.el9ap | 0:2.6.17-1.el9ap |
| Red Hat:ansible_automation_platform:2.6::el9 | automation-platform-ui | before 0:2.6.11-1.el9ap | 0:2.6.11-1.el9ap |
| Red Hat:ansible_automation_platform:2.6::el9 | python3.12-gitpython | before 0:3.1.50-1.el9ap | 0:3.1.50-1.el9ap |
| Red Hat:ansible_automation_platform:2.6::el9 | python3.12-pulpcore | before 0:3.49.63-2.el9ap | 0:3.49.63-2.el9ap |
| Red Hat:enterprise_linux:10.2 | python3.14-pip | before 0:25.2-3.el10_2.5 | 0:25.2-3.el10_2.5 |
| Red Hat:enterprise_linux:10.2 | python3.14-pip-wheel | before 0:25.2-3.el10_2.5 | 0:25.2-3.el10_2.5 |
| Red Hat:enterprise_linux:9::appstream | python3.14-pip | before 0:25.2-3.el9_8.5 | 0:25.2-3.el9_8.5 |
+20
Same product
pypa: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-20225An issue was discovered in pip (all versions) because it installs the version with the highest version number, even if the user had intended32Monitor
- CVE-2019-20916The pip package before 19.2 for Python allows Directory Traversal when a URL is given in an install command, because a Content-Disposition h31Monitor
- CVE-2013-1629pip before 1.3 uses HTTP to retrieve packages from the PyPI repository, and does not perform integrity checks on package contents, which all29Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-3572Nov 10, 2021 · A flaw was found in python-pip in the way it handled Unicode separators in git references.23Monitor
- ← EarlierCVE-2023-5752Oct 25, 2023 · Mercurial configuration injectable in repo revision when installing via pip13Monitor
- Later →CVE-2026-13346Jul 29, 2026 · pip absolute path traversal during download from malicious package indexes22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Python Packaging Authority pip | 26.1.2 | Vendor (CNA) |
| azl3 python-pip 24.2-8 on Azure Linux 3.0 | 24.2-9 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 python-pip 24.2-9 on Azure Linux 3.0 | 24.2-9 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 python-virtualenv 20.36.1-4 on Azure Linux 3.0 | 20.36.1-5 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:python3.14-pip | 25.2-3.el10_2.5 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:python3.14-pip-wheel | 25.2-3.el10_2.5 · AlmaLinux:10 | Package registry (OSV) |
| debian:python-pip | 26.1.2+dfsg-1 · Debian:14 | Package registry (OSV) |
| opensuse:python-pip | 26.1.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:pip | 26.1.2 | Package registry (OSV) |
| red hat:ansible-core | 2:2.16.19-1.el10ap · Red Hat:ansible_automation_platform_developer:2.6::el10 | Package registry (OSV) |
| red hat:automation-controller-venv-tower | 0:4.7.14-3.el9ap · Red Hat:ansible_automation_platform:2.6::el9 | Package registry (OSV) |
| red hat:automation-gateway-proxy | 0:2.6.17-1.el9ap · Red Hat:ansible_automation_platform:2.6::el9 | Package registry (OSV) |
| red hat:automation-gateway-proxy-debugsource | 0:2.6.17-1.el9ap · Red Hat:ansible_automation_platform:2.6::el9 | Package registry (OSV) |
| red hat:automation-gateway-proxy-server | 0:2.6.17-1.el9ap · Red Hat:ansible_automation_platform:2.6::el9 | Package registry (OSV) |
| red hat:automation-platform-ui | 0:2.6.11-1.el9ap · Red Hat:ansible_automation_platform:2.6::el9 | Package registry (OSV) |
| red hat:python-pip | 0:26.1.1-3.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python-pip-wheel | 0:26.1.1-3.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python3-pip | 0:26.1.1-3.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python3.12-pulpcore | 0:3.49.63-2.el9ap · Red Hat:ansible_automation_platform:2.6::el9 | Package registry (OSV) |
| red hat:python3.14-pip | 0:25.2-3.el10_2.5 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:python3.14-pip-wheel | 0:25.2-3.el10_2.5 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:receptor | 0:1.6.6-1.el10ap · Red Hat:ansible_automation_platform:2.6::el10 | Package registry (OSV) |
| rocky linux:python3.14-pip | 0:25.2-3.el10_2.5 · Rocky Linux:10 | Package registry (OSV) |
| suse:python | 2.7.18-150000.123.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | Package registry (OSV) |
| suse:python-base | 2.7.18-150000.123.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7 | Package registry (OSV) |
| suse:python-doc | 2.7.18-33.82.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:python-pip | 25.0.1-160000.5.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
| suse:python3 | 3.4.10-25.191.2 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:python3-base | 3.4.10-25.191.2 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
| suse:python36 | 3.6.15-116.1 · SUSE:Linux Enterprise Server 12 SP5-LTSS | Package registry (OSV) |
+1
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Lumír Balharreporter
- Damian Shaw (https://github.com/notatallshaw)remediation developer
- Gregory P. Smith (https://github.com/gpshead)remediation reviewer
- Pradyun Gedam (https://github.com/pradyunsg)remediation reviewer
- Paul Moore (https://github.com/pfmoore)remediation reviewer
- Jannis Leidel (https://github.com/jezdez)remediation reviewer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:N/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
nvd-secondary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- mail.python.org/archives/list/security-announce@python.org/thread/YV63UET5D3OOJY7O4M5XCVYO2YM4NBYJ/
- www.openwall.com/lists/oss-security/2026/06/01/5
- access.redhat.com/errata/RHSA-2026:33313
- access.redhat.com/errata/RHSA-2026:34374
- access.redhat.com/errata/RHSA-2026:34456
- access.redhat.com/errata/RHSA-2026:34739
- access.redhat.com/errata/RHSA-2026:34740
- access.redhat.com/errata/RHSA-2026:34741
- access.redhat.com/errata/RHSA-2026:34748
- access.redhat.com/errata/RHSA-2026:34749
- access.redhat.com/errata/RHSA-2026:34750
- access.redhat.com/errata/RHSA-2026:34752
- access.redhat.com/errata/RHSA-2026:34756
- access.redhat.com/errata/RHSA-2026:34758
- access.redhat.com/errata/RHSA-2026:34760
- access.redhat.com/errata/RHSA-2026:34765
- access.redhat.com/errata/RHSA-2026:34772
- access.redhat.com/errata/RHSA-2026:34773
- access.redhat.com/errata/RHSA-2026:34774
Vendor advisories and official records. Exploit/PoC links are deliberately left out.