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

Tarfile.extract() doesn't fully respect filter parameter

Python Software Foundation · CPython

2.0LowCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

Low 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 1 structured product or package state 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 severityLowOperational priority:Low, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.48% 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 Software Foundation CPython 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: No default targetRemediation target: Normal maintenance

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 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

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

18 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 1 affected package state 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
Alpine v3.23v3.23 · mainpython3Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.3.12.14-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainpython3Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.3.12.14-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.21v3.21 · mainpython3Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.3.12.14-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcejythonNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian trixietrixie · sourcepypy3Affected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian trixietrixie · sourcepython3.13Vendor fix publishedDebian records a fixed source-package version for this release.3.13.5-2+deb13u5Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcejythonNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcepypy3Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcepython3.11Not affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcejythonNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepypy3Vendor fix publishedDebian records a fixed source-package version for this release.8.0.0+dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepython3.13Vendor fix publishedDebian records a fixed source-package version for this release.3.13.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcepython3.14Vendor fix publishedDebian records a fixed source-package version for this release.3.14.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcejythonNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepypy3Vendor fix publishedDebian records a fixed source-package version for this release.8.0.0+dfsg-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepython3.13Vendor fix publishedDebian records a fixed source-package version for this release.3.13.15-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcepython3.14Vendor fix publishedDebian records a fixed source-package version for this release.3.14.7-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivepython3.12Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.3.12.3-1ubuntu0.17Canonical Ubuntu Security ↗Source updated 5 Oct 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.

1 current
CVE-2026-4360 · CSAF 2.0 · revision 3 · status not statedRed Hat Product Securitypython: Python Tarfile: Unexpected file ownership when extracting hardlinks
101 known affected

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

  • exploit-intelligence-tech-preview/vulnerability-analysis-rhel9 as a component of Exploit Intelligence
  • rhaii/model-opt-cuda-rhel9 as a component of Red Hat AI Inference Server
  • rhaii/vllm-cpu-rhel9 as a component of Red Hat AI Inference Server
  • rhaii/vllm-cuda-rhel9 as a component of Red Hat AI Inference Server
  • rhaii/vllm-gaudi-rhel9 as a component of Red Hat AI Inference Server
  • rhaii/vllm-neuron-rhel9 as a component of Red Hat AI Inference Server
  • rhaii/vllm-rocm-rhel9 as a component of Red Hat AI Inference Server
  • rhaii/vllm-spyre-rhel9 as a component of Red Hat AI Inference Server
  • rhaii/vllm-tpu-rhel9 as a component of Red Hat AI Inference Server
  • rhaiis/model-opt-cuda-rhel9 as a component of Red Hat AI Inference Server
  • rhaiis/vllm-cpu-rhel9 as a component of Red Hat AI Inference Server
  • rhaiis/vllm-cuda-rhel9 as a component of Red Hat AI Inference Server
Summary
A flaw was found in the Python `Tarfile.extract()` function. This vulnerability occurs when processing untrusted tar files containing hardlinks, as the `filter` parameter is not correctly enforced. An attacker could exploit this to write files with unintended user or group ownership, potentially leading to unauthorized modifications or privilege issues on the system.
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-40336

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

Low 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 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Tarfile.extract() function, the filter parameter is not passed properly when extracting hardlinks. An affected system that extracts content from untrusted tar files could end up writing files with an unexpected uid/gid despite the user passing filter='data' to the extract() function.

What

In the Tarfile.extract() function, the filter parameter is not passed properly when extracting hardlinks. An affected system that extracts content from untrusted tar files could end up writing files with an unexpected uid/gid despite the user passing filter='data' to the extract() function.

Why

The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.

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

In the Tarfile.extract() function, the filter parameter is not passed properly when extracting hardlinks. An affected system that extracts content from untrusted tar files could end up writing files with an unexpected uid/gid despite the user passing filter='data' to the extract() function.

Why

The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.

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 → Improper Preservation of Permissions → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
High: elevated access is required
User interaction
Passive interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-281 ↗

CWE-281: Improper Preservation of Permissions. The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.

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:L/AT:P/PR:H/UI:P/VC:N/VI:L/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.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATPresentAttack requirements: A particular deployment or execution condition must be present.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UIPassiveUser interaction: A user must unknowingly interact with the vulnerable system.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VILowVulnerable-system integrity: A successful attack can cause a limited 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-281
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-20260701Security Bulletin 1 July 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 1 July 2026, published on 1 July 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-42505 Référence CVE CVE-2026-42507 https://www.cve.org/CVERecord?id=CVE-2026-42507 Référence CVE CVE-2026-42508 https://www.cve.org/CVERecord?id=CVE-2026-42508 Référence CVE CVE-2026-42764 https://www.cve.org/CVERecord?id=CVE-2026-42764 Référence CVE CVE-2026-42766 https://www.cve.org/CVERecord?id=CVE-2026-42766 Référence CVE CVE-2026-42767 https://www.cve.org/CVERecord?id=CVE-2026-42767 Référence CVE CVE-2026-42768 https://www.cve.org/CVERecord?id=CVE-2026-42768 Référence CVE CVE-2026-42769 https://www.cve.org/CVERecord?id=CVE-2026-42769 Référence CVE CVE-2026-42770 https://www.cve.org/CVERecord?id=CVE-2026-42770 Référence CVE CVE-2026-4360 https://www.cve.org/CVERecord?id=CVE-2026-4360 Référence CVE CVE-2026-4539 https://www.cve.org/CVERecord?id=CVE-2026-4539 Référence CVE CVE-2026-45445 https://www.cve.org/CVERecord?id=CVE-2026-45445 Référence CVE CVE-2026-45446 https://www.cve.org/CVERecord?id=CVE-2026-45446 Référence CVE CVE-2026-45447 https://www.cve.org/CVERecord?id=CVE-2026-45447 Référence CVE CVE-2026-46595 https://www.cve.org/CVERecord?id=CVE-2026-46595 Référence CVE CVE-2026-46597 https://www.cve.org/CVERecord?id=CVE-2026-46597 Référence CVE CVE-2026-46598 https://www.cve.org/CVERecord?id=CVE-2026-46598 Référence CVE CVE-2026-46600 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0828Vulnérabilité dans CPython

Une vulnérabilité a été découverte dans CPython. Elle permet à un attaquant de provoquer un contournement de la politique de sécurité.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-022943Python Software FoundationのPythonにおけるパーミッションの不適切な保持に関する脆弱性

Tarfile.extract() 関数において、ハードリンクを抽出する際に filter パラメータが適切に渡されません。信頼できない tar ファイルからコンテンツを抽出する場合、影響を受けたシステムではユーザーが extract() 関数に filter='data' を渡したにもかかわらず、予期しない uid/gid でファイルが書き込まれてしまう可能性があります。

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
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 30 Jun 2026 · Last source change 13 Aug 2026, 00:27 UTC · CWE-281 · Improper Preservation of Permissions

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-40336
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

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
    < 3.10.21; 3.11.0 < 3.11.16; 3.12.0 < 3.12.14; 3.13.0 < 3.13.15; 3.14.0 < 3.14.7; 3.15.0a1 < 3.15.0b4 · 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
    < 3.10.21; 3.11.0 < 3.11.16; 3.12.0 < 3.12.14; 3.13.0 < 3.13.15; 3.14.0 < 3.14.7; 3.15.0a1 < 3.15.0b4 · 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 ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-4360 · cve.blacktree.nl