How severe is CVE-2026-1703?

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

Which packages are affected by CVE-2026-1703?

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

How do I fix CVE-2026-1703?

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

How do I detect CVE-2026-1703 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-1703 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-1703 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-1703 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-1703?

CVE-2026-1703 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 38th 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-1703?

CVE-2026-1703 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-1703 published, and has it been updated?

CVE-2026-1703 was published on February 2, 2026 and was last updated on October 28, 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-1703 — pip

Fix: pypa/pip@8e227a9

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

Limited path traversal when installing wheel archives

Also known asGHSA-6vgw-5pg2-w6jpPYSEC-2026-1796

Published

Feb 2, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 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-1703.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs38th percentile — riskier than 38% 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

When pip is installing and extracting a maliciously crafted wheel archive, files may be extracted outside the installation directory. The path traversal is limited to prefixes of the installation directory, thus isn't able to inject or overwrite executable files in typical situations.

Affected Packages

1 total 1 fixed

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

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.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-1703 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 HatLow

This LOW impact flaw in pip allows information disclosure via path traversal when installing crafted wheel archives. While files may be extracted outside the installation directory, the traversal is limited to prefixes of the installation directory, preventing injection or overwriting of executable files in typical…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

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

Product	Fixed in	Advisory
Red Hat Hardened Images	`python-pip-main-26.0.1-2.1.hum1`	RHSA-2026:7610
Red Hat OpenShift AI 3.0	`rhai/base-image-rocm-rhel9:1793041981`	RHSA-2026:91219
Red Hat OpenShift AI 3.0	`rhai/base-image-cpu-rhel9:1793042072`	RHSA-2026:91232
Red Hat OpenShift AI 3.0	`rhai/base-image-cuda-rhel9:1793042067`	RHSA-2026:91236
Red Hat OpenShift AI 3.0	`rhai/base-image-cpu-rhel9:1793329709`	RHSA-2026:94459
Red Hat OpenShift AI 3.0	`rhai/base-image-cuda-rhel9:1793328358`	RHSA-2026:94476

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-1703 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works