Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2026-11940

Published Jun 23, 2026 CWE-22 EPSS 0.75% (52th pctl)

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.

References

GitHub github.com/python/cpython/commit/0f852b3f07dd8e71e40326a51c02afbf16a42cc5 GitHub github.com/python/cpython/commit/27dd970bf6b17ebca7c8ed486a40ab043ed7af8f GitHub github.com/python/cpython/commit/672825e2f36a57e173959b0d9d409d4560dab8df GitHub github.com/python/cpython/commit/771d12dda5140313db0ac550292987975651bbde GitHub github.com/python/cpython/commit/79c06bd5c6afa3c440d50faf7ee1b147c8832b4c GitHub github.com/python/cpython/commit/be13e86f6b9788a6f4d0419dffef72cbae5865c9 GitHub github.com/python/cpython/commit/e5fdbd8d5aa923bd9111b112ea73bd6ec7c47877 GitHub github.com/python/cpython/issues/151558 GitHub github.com/python/cpython/pull/151559 Ref mail.python.org/archives/list/[email protected]/thread/LD6QIISNQFQYOIEPJNEUIPV7S3V76FZH/

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's AI-powered security agents can automatically detect CVE-2026-11940 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.

How CyberStrike Helps

Autonomous Discovery

AI agents map your attack surface to find vulnerabilities like this one.
Continuous Pentesting

Automated penetration testing that runs continuously, not just quarterly.
Code Review

AI-driven PR review catches vulnerable dependencies before they ship.
HackBrowser

Browser-based exploitation validates findings with real proof-of-concept.
Browse by year 2026 2025 2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999