Skip to content
Noroxi
NVD / CVE Program· CNA PSF

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.

MediumCVSS 4.1 · v4.0—No exploit Fix available
Published
Jun 1, 2026
Updated
Sep 16, 2026
EPSS
0.3% · 25th percentile

Report tools

JSON

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.

Follow CVE-2026-8643

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
pypapip

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.

EcosystemPackageAffected rangeFix
AlmaLinux:10python3.14-pipbefore 25.2-3.el10_2.525.2-3.el10_2.5
AlmaLinux:10python3.14-pip-wheelbefore 25.2-3.el10_2.525.2-3.el10_2.5
AlmaLinux:9python3.14-pipbefore 25.2-3.el9_8.525.2-3.el9_8.5
AlmaLinux:9python3.14-pip-wheelbefore 25.2-3.el9_8.525.2-3.el9_8.5
Debian:12python-pipfrom 0—
Debian:14python-pipbefore 26.1.2+dfsg-126.1.2+dfsg-1
openSUSE:Leap 16.0python-pipbefore 25.0.1-160000.5.125.0.1-160000.5.1
openSUSE:Tumbleweedpython-pipbefore 26.1.2-1.126.1.2-1.1
PyPIpipbefore 26.1.226.1.2
Red Hat:ansible_automation_platform_developer:2.6::el10ansible-corebefore 2:2.16.19-1.el10ap2:2.16.19-1.el10ap
Red Hat:ansible_automation_platform_developer:2.6::el9ansible-corebefore 1:2.16.19-1.el9ap1:2.16.19-1.el9ap
Red Hat:ansible_automation_platform_developer:2.6::el9receptorbefore 0:1.6.6-1.el9ap0:1.6.6-1.el9ap
Red Hat:ansible_automation_platform:2.6::el10receptorbefore 0:1.6.6-1.el10ap0:1.6.6-1.el10ap
Red Hat:ansible_automation_platform:2.6::el9automation-controller-venv-towerbefore 0:4.7.14-3.el9ap0:4.7.14-3.el9ap
Red Hat:ansible_automation_platform:2.6::el9automation-gateway-proxybefore 0:2.6.17-1.el9ap0:2.6.17-1.el9ap
Red Hat:ansible_automation_platform:2.6::el9automation-gateway-proxy-debugsourcebefore 0:2.6.17-1.el9ap0:2.6.17-1.el9ap
Red Hat:ansible_automation_platform:2.6::el9automation-gateway-proxy-serverbefore 0:2.6.17-1.el9ap0:2.6.17-1.el9ap
Red Hat:ansible_automation_platform:2.6::el9automation-gateway-proxy-server-debuginfobefore 0:2.6.17-1.el9ap0:2.6.17-1.el9ap
Red Hat:ansible_automation_platform:2.6::el9automation-platform-uibefore 0:2.6.11-1.el9ap0:2.6.11-1.el9ap
Red Hat:ansible_automation_platform:2.6::el9python3.12-gitpythonbefore 0:3.1.50-1.el9ap0:3.1.50-1.el9ap
Red Hat:ansible_automation_platform:2.6::el9python3.12-pulpcorebefore 0:3.49.63-2.el9ap0:3.49.63-2.el9ap
Red Hat:enterprise_linux:10.2python3.14-pipbefore 0:25.2-3.el10_2.50:25.2-3.el10_2.5
Red Hat:enterprise_linux:10.2python3.14-pip-wheelbefore 0:25.2-3.el10_2.50:25.2-3.el10_2.5
Red Hat:enterprise_linux:9::appstreampython3.14-pipbefore 0:25.2-3.el9_8.50:25.2-3.el9_8.5

+20

Same product

pypa: all records

Other 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 intended
    32Monitor
  • 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 h
    31Monitor
  • 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 all
    29Monitor

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 pip
    13Monitor
  • Later →CVE-2026-13346Jul 29, 2026 · pip absolute path traversal during download from malicious package indexes
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Python Packaging Authority pip26.1.2Vendor (CNA)
azl3 python-pip 24.2-8 on Azure Linux 3.024.2-9 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 python-pip 24.2-9 on Azure Linux 3.024.2-9 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 python-virtualenv 20.36.1-4 on Azure Linux 3.020.36.1-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:python3.14-pip25.2-3.el10_2.5 · AlmaLinux:10Package registry (OSV)
almalinux:python3.14-pip-wheel25.2-3.el10_2.5 · AlmaLinux:10Package registry (OSV)
debian:python-pip26.1.2+dfsg-1 · Debian:14Package registry (OSV)
opensuse:python-pip26.1.2-1.1 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:pip26.1.2Package registry (OSV)
red hat:ansible-core2:2.16.19-1.el10ap · Red Hat:ansible_automation_platform_developer:2.6::el10Package registry (OSV)
red hat:automation-controller-venv-tower0:4.7.14-3.el9ap · Red Hat:ansible_automation_platform:2.6::el9Package registry (OSV)
red hat:automation-gateway-proxy0:2.6.17-1.el9ap · Red Hat:ansible_automation_platform:2.6::el9Package registry (OSV)
red hat:automation-gateway-proxy-debugsource0:2.6.17-1.el9ap · Red Hat:ansible_automation_platform:2.6::el9Package registry (OSV)
red hat:automation-gateway-proxy-server0:2.6.17-1.el9ap · Red Hat:ansible_automation_platform:2.6::el9Package registry (OSV)
red hat:automation-platform-ui0:2.6.11-1.el9ap · Red Hat:ansible_automation_platform:2.6::el9Package registry (OSV)
red hat:python-pip0:26.1.1-3.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python-pip-wheel0:26.1.1-3.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3-pip0:26.1.1-3.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:python3.12-pulpcore0:3.49.63-2.el9ap · Red Hat:ansible_automation_platform:2.6::el9Package registry (OSV)
red hat:python3.14-pip0:25.2-3.el10_2.5 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:python3.14-pip-wheel0:25.2-3.el10_2.5 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:receptor0:1.6.6-1.el10ap · Red Hat:ansible_automation_platform:2.6::el10Package registry (OSV)
rocky linux:python3.14-pip0:25.2-3.el10_2.5 · Rocky Linux:10Package registry (OSV)
suse:python2.7.18-150000.123.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7Package registry (OSV)
suse:python-base2.7.18-150000.123.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7Package registry (OSV)
suse:python-doc2.7.18-33.82.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:python-pip25.0.1-160000.5.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:python33.4.10-25.191.2 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:python3-base3.4.10-25.191.2 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:python363.6.15-116.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage 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.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

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

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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const file = path.join(ROOT, req.query.name);res.sendFile(file);

Fixed

ts
const file = path.resolve(ROOT, req.query.name);if (!file.startsWith(ROOT + path.sep)) {  return res.sendStatus(400);}res.sendFile(file);

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records