How severe is GHSA-qwm4-qh6w-59xr?

No CVSS score has been assigned to GHSA-qwm4-qh6w-59xr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qwm4-qh6w-59xr?

GHSA-qwm4-qh6w-59xr affects the following packages: pip (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-qwm4-qh6w-59xr?

Update pip to 26.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qwm4-qh6w-59xr is resolved across your whole dependency graph.

How do I detect GHSA-qwm4-qh6w-59xr 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 GHSA-qwm4-qh6w-59xr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-qwm4-qh6w-59xr actively exploited in the wild?

No public exploit code has been indexed for GHSA-qwm4-qh6w-59xr 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 GHSA-qwm4-qh6w-59xr?

GHSA-qwm4-qh6w-59xr has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th 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 GHSA-qwm4-qh6w-59xr?

GHSA-qwm4-qh6w-59xr is classified as CWE-36 (CWE-36). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qwm4-qh6w-59xr published, and has it been updated?

GHSA-qwm4-qh6w-59xr was published on July 29, 2026 and was last updated on September 10, 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

pip would incorrectly handle doubly-encoded package URLs from indexesGHSA-qwm4-qh6w-59xr

Fix: pypa/pip#14110

GHSA-qwm4-qh6w-59xr is a CWE-36 vulnerability in pip. A fix is available for pip — see the affected versions and patch details below.

Also known asCVE-2026-13346PYSEC-2026-3721

Published

Jul 29, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 16, 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 GHSA-qwm4-qh6w-59xr.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs20th percentile — riskier than 20% 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 incorrectly handle doubly-encoded package URLs from indexes allowing for files to be installed to arbitrary locations on disk even when installing wheels.

This vulnerability requires downloading or installing a package from a malicious package index to succeed, malicious packages alone are not able to exploit this vulnerability. Note that this vulnerability only materially impacts users running pip download with the --only-binary option as installing source distributions from an untrusted index is already an unsafe operation that executes code during install time.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

pippypa

< 26.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.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qwm4-qh6w-59xr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

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 HatModerate

Note that this vulnerability only materially impacts users running pip download with the --only-binary option as installing source distributions from an untrusted index is already an unsafe operation that executes code during install time.

Product	Fixed in	Advisory
Red Hat AI Inference Server 3.5	`rhaii/vllm-gaudi-rhel9:1791427182`	RHSA-2026:82061
Red Hat AI Inference Server 3.5	`rhaii/vllm-cuda-rhel9:1791473631`	RHSA-2026:82368
Red Hat AI Inference Server 3.5	`rhaii/vllm-cpu-rhel9:1791473614`	RHSA-2026:82415
Red Hat Hardened Images	`python-pip-main-26.2-0.1.hum1`	RHSA-2026:48788

Frequently Asked Questions

pip would incorrectly handle doubly-encoded package URLs from indexes allowing for files to be installed to arbitrary locations on disk even when installing wheels. This vulnerability requires downloading or installing a package from a malicious package index to succeed, malicious packages alone are not able to exploit this vulnerability. Note that this vulnerability only materially impacts users running `pip download` with the `--only-binary` option as installing source distributions from an untrusted index is already an unsafe operation that executes code during install time.

O3 Security · Impact-Aware SCA

Is GHSA-qwm4-qh6w-59xr in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works