Quick answers
- Is CVE-2026-11940 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11940 being exploited in the wild.
- How severe is CVE-2026-11940?
- Informational severity, with a CVSS score of 7.8, published 23 June 2026.
- Which products and versions are affected?
- Python Software Foundation CPython < 3.16.0.
- Is there a fix for CVE-2026-11940?
- A patch was published on 2026-06-23: Fix merged into CPython main branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-11940 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-11940?
- Check whether you run Python Software Foundation CPython at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in the Python `tarfile` module's `extractall()` function. When using the 'data' or 'tar' filters, a bypass is possible using a crafted archive where a hardlink references a symlink located deeper in the directory structure than the hardlink itself. The extraction fallback mechanism validates the symlink at its original archived location but recreates it at the shallower path of the hardlink; this allows a relative symlink target, previously judged safe by the filter, to resolve to a location outside the intended destination directory. This is an incomplete fix for CVE-2025-4330 and allows for arbitrary file reads or writes upon extraction. The issue is addressed in CPython versions leading up to 3.16.0.
Affected products
- Python Software Foundation CPython < 3.16.0
Timeline
- 2026-06-16: disclosed: Issue reported on GitHub
- 2026-06-23: patched: Fix merged into CPython main branch
- 2026-06-23: advisory: Security announcement and CVE published