Menu

Star on GitHub · 3.2k

CVE-2026-11940

tarfile.extractall() with the 'data' or 'tar' filter could be bypassed by a crafted archive where a hardlink references a symlink stored at a deeper name than the hardlink itself.

Published Jun 23, 2026CWE-22EPSS 0.75%

Overview

CVE-2026-11940 is a known-severity vulnerability. It was published on June 23, 2026.

Technical description

tarfile.extractall() with the 'data' or 'tar'

filter could be bypassed by a crafted archive where a hardlink

references a symlink stored at a deeper name than the hardlink itself. 

The extraction fallback validated the symlink at it's archived location

but recreated it at the hardlink's shallower

path, letting a relative

target the filter judged contained escape the destination directory. 

This allowed a malicious tar archive to create a symlink pointing

outside the destination, enabling out-of-destination file reads or

writes. This was an incomplete fix of CVE-2025-4330.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-11940?

CVE-2026-11940 is a known-severity vulnerability. It was published on June 23, 2026.

How severe is CVE-2026-11940?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-11940?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-11940?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-11940 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.