BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-13346High confidence

pip absolute path traversal during download from malicious package indexes

Python Packaging Authority · pip

5.6MediumCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.29% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Python Packaging Authority pip and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

6 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcepython-pipAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcepython-pipAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepython-pipAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepython-pipAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appspython-pipUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivepipenvUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges3 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
PyPIpipECOSYSTEM: introduced 0; fixed 26.2.026.2.0OSV record ↗aggregator derived · 10 Sep 2026
PyPIpipECOSYSTEM: introduced 0; fixed 26.226.2OSV record ↗source linked ecosystem record · 10 Sep 2026
pippip< 26.2.026.2.0GitHub advisory ↗github reviewed aggregator · 1 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

2 current
CVE-2026-13346 · CSAF 2.0 · revision 14 · interimSUSE Product Security TeamCVE-2026-13346
572 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • python3 as component of SUSE Linux Enterprise Desktop 15 SP7
  • python3-curses as component of SUSE Linux Enterprise Desktop 15 SP7
  • python3-dbm as component of SUSE Linux Enterprise Desktop 15 SP7
  • python3-idle as component of SUSE Linux Enterprise Desktop 15 SP7
  • python3-tk as component of SUSE Linux Enterprise Desktop 15 SP7
  • python311 as component of SUSE Linux Enterprise Desktop 15 SP7
  • python311-curses as component of SUSE Linux Enterprise Desktop 15 SP7
  • python311-dbm as component of SUSE Linux Enterprise Desktop 15 SP7
  • python311-idle as component of SUSE Linux Enterprise Desktop 15 SP7
  • python311-tk as component of SUSE Linux Enterprise Desktop 15 SP7
  • python313 as component of SUSE Linux Enterprise Desktop 15 SP7
  • python313-curses as component of SUSE Linux Enterprise Desktop 15 SP7
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
CVE-2026-13346 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitypip: pip: Arbitrary file installation via malicious package indexes
13 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • python3-pip as a component of Red Hat Enterprise Linux 10
  • python3-pip-wheel as a component of Red Hat Enterprise Linux 10
  • python-pip.src as a component of Red Hat Enterprise Linux 7
  • python3-pip as a component of Red Hat Enterprise Linux 7
  • platform-python-pip as a component of Red Hat Enterprise Linux 8
  • python-pip.src as a component of Red Hat Enterprise Linux 8
  • python3-pip as a component of Red Hat Enterprise Linux 8
  • python3-pip-wheel as a component of Red Hat Enterprise Linux 8
  • python-pip.src as a component of Red Hat Enterprise Linux 9
  • python3-pip as a component of Red Hat Enterprise Linux 9
  • python3-pip-wheel as a component of Red Hat Enterprise Linux 9
  • openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4
Summary
A flaw was found in pip. When processing doubly-encoded package URLs from malicious package indexes, pip incorrectly handles the file paths. A remote attacker could exploit this by convincing a user to download or install a package from such an index. This could allow for files to be installed to arbitrary locations on the system, potentially leading to system compromise. This vulnerability primarily affects users utilizing the `pip download` command with the `--only-binary` option.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-50467

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 4 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize absolute path sequences such as /abs/path that can resolve to a location that is outside of that directory.

How

An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize absolute path sequences such as /abs/path that can resolve to a location that is outside of that directory.

How

An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Absolute Path Traversal → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
High: elevated access is required
User interaction
Active interaction required
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-36 ↗

CWE-36: Absolute Path Traversal. The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize absolute path sequences such as /abs/path that can resolve to a location that is outside of that directory.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UIActiveUser interaction: A user must take a deliberate action for exploitation to succeed.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VANoneVulnerable-system availability: No direct loss is represented by this metric.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkCWE-36
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20260805Security Bulletin 5 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 5 Aug 2026, published on 5 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1249Multiples vulnérabilités dans les produits VMware

d?id=CVE-2026-11822 Référence CVE CVE-2026-11824 https://www.cve.org/CVERecord?id=CVE-2026-11824 Référence CVE CVE-2026-11940 https://www.cve.org/CVERecord?id=CVE-2026-11940 Référence CVE CVE-2026-11972 https://www.cve.org/CVERecord?id=CVE-2026-11972 Référence CVE CVE-2026-11979 https://www.cve.org/CVERecord?id=CVE-2026-11979 Référence CVE CVE-2026-12003 https://www.cve.org/CVERecord?id=CVE-2026-12003 Référence CVE CVE-2026-12087 https://www.cve.org/CVERecord?id=CVE-2026-12087 Référence CVE CVE-2026-12912 https://www.cve.org/CVERecord?id=CVE-2026-12912 Référence CVE CVE-2026-13221 https://www.cve.org/CVERecord?id=CVE-2026-13221 Référence CVE CVE-2026-13346 https://www.cve.org/CVERecord?id=CVE-2026-13346 Référence CVE CVE-2026-13506 https://www.cve.org/CVERecord?id=CVE-2026-13506 Référence CVE CVE-2026-13595 https://www.cve.org/CVERecord?id=CVE-2026-13595 Référence CVE CVE-2026-13757 https://www.cve.org/CVERecord?id=CVE-2026-13757 Référence CVE CVE-2026-14164 https://www.cve.org/CVERecord?id=CVE-2026-14164 Référence CVE CVE-2026-14257 https://www.cve.org/CVERecord?id=CVE-2026-14257 Référence CVE CVE-2026-14456 https://www.cve.org/CVERecord?id=CVE-2026-14456 Référence CVE CVE-2026-14457 https://www.cve.org/CVERecord?id=CVE-2026-14457 Référence CVE CVE-2026-15308 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-029511Python Packaging Authorityのpipにおける絶対パストラバーサルに関する脆弱性

pip は、インデックスから二重にエンコードされたパッケージURLを誤って処理してしまい、ホイールをインストールする際であっても、ファイルが任意のディスク上の場所にインストールされる可能性があります。この脆弱性を悪用するには、悪意のあるパッケージインデックスからパッケージをダウンロードまたはインストールする必要があり、悪意のあるパッケージ単体ではこの脆弱性を悪用できません。なお、この脆弱性は、`pip download` コマンドを `--only-binary` オプション付きで実行するユーザーに主に影響を与えます。信頼できないインデックスからソースディストリビューションをインストールすることは、すでにコードがインストール時に実行されるため、安全でない操作となります。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 29 Jul 2026 · Last source change 29 Jul 2026, 20:21 UTC · CWE-36 · Absolute Path Traversal

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-50467
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 26.2 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    < 26.2 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    python3-pip as a component of Red Hat Enterprise Linux 10; python3-pip-wheel as a component of Red Hat Enterprise Linux 10; python-pip.src as a component of Red Hat Enterprise Linux 7; python3-pip as a component of Red Hat Enterprise Linux 7; platform-python-pip as a component of Red Hat Enterprise Linux 8; python-pip.src as a component of Red Hat Enterprise Linux 8; python3-pip as a component of Red Hat Enterprise Linux 8; python3-pip-wheel as a component of Red Hat Enterprise Linux 8; python-pip.src as a component of Red Hat Enterprise Linux 9; python3-pip as a component of Red Hat Enterprise Linux 9; python3-pip-wheel as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: python-pip-main@noarch as a component of Red Hat Hardened Images; python-pip-main@src as a component of Red Hat Hardened Images
    After
    python3-pip as a component of Red Hat Enterprise Linux 10; python3-pip-wheel as a component of Red Hat Enterprise Linux 10; python-pip.src as a component of Red Hat Enterprise Linux 7; python3-pip as a component of Red Hat Enterprise Linux 7; platform-python-pip as a component of Red Hat Enterprise Linux 8; python-pip.src as a component of Red Hat Enterprise Linux 8; python3-pip as a component of Red Hat Enterprise Linux 8; python3-pip-wheel as a component of Red Hat Enterprise Linux 8; python-pip.src as a component of Red Hat Enterprise Linux 9; python3-pip as a component of Red Hat Enterprise Linux 9; python3-pip-wheel as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-8 as a component of Red Hat OpenShift Container Platform 4; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: python-pip-main@noarch as a component of Red Hat Hardened Images; python-pip-main@src as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    python3-pip as a component of Red Hat Enterprise Linux 10; python3-pip-wheel as a component of Red Hat Enterprise Linux 10; python-pip.src as a component of Red Hat Enterprise Linux 7; python3-pip as a component of Red Hat Enterprise Linux 7; platform-python-pip as a component of Red Hat Enterprise Linux 8; python-pip.src as a component of Red Hat Enterprise Linux 8; python3-pip as a component of Red Hat Enterprise Linux 8; python3-pip-wheel as a component of Red Hat Enterprise Linux 8; python-pip.src as a component of Red Hat Enterprise Linux 9; python3-pip as a component of Red Hat Enterprise Linux 9; python3-pip-wheel as a component of Red Hat Enterprise Linux 9; rhcos as a component of Red Hat OpenShift Container Platform 4 · Fixed: python-pip-main@noarch as a component of Red Hat Hardened Images; python-pip-main@src as a component of Red Hat Hardened Images
    After
    python3-pip as a component of Red Hat Enterprise Linux 10; python3-pip-wheel as a component of Red Hat Enterprise Linux 10; python-pip.src as a component of Red Hat Enterprise Linux 7; python3-pip as a component of Red Hat Enterprise Linux 7; platform-python-pip as a component of Red Hat Enterprise Linux 8; python-pip.src as a component of Red Hat Enterprise Linux 8; python3-pip as a component of Red Hat Enterprise Linux 8; python3-pip-wheel as a component of Red Hat Enterprise Linux 8; python-pip.src as a component of Red Hat Enterprise Linux 9; python3-pip as a component of Red Hat Enterprise Linux 9; python3-pip-wheel as a component of Red Hat Enterprise Linux 9; openshift/ose-rhel-coreos-9 as a component of Red Hat OpenShift Container Platform 4 · Fixed: python-pip-main@noarch as a component of Red Hat Hardened Images; python-pip-main@src as a component of Red Hat Hardened Images
    Red Hat Product Security ↗
  4. Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/14110; added remediation: github.com/14110.
    Before
    no authoritative guidance recorded
    After
    patch: github.com/14110 · remediation: github.com/14110
    cna@python.org ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 26.2 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 26.2 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  6. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    cna@python.org ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-50467↗Vendor CSAF · SUSE Product Security Team↗Red Hat Product Security security advisory↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-13346 · cve.blacktree.nl