Quick answers
- Is CVE-2026-87910 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-87910 being exploited in the wild.
- How severe is CVE-2026-87910?
- Informational severity, published 11 September 2026.
- Which products and versions are affected?
- Python CPython 3.12, 3.13.
- Is there a fix for CVE-2026-87910?
- A patch was published on 2026-09-11. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-87910 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-87910?
- Check whether you run Python 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
The tarfile filter function is called twice during link extraction fallback—once for the target member and once for the link location—but the return value from one call is ignored. If either call returns None (indicating rejection), the member should be skipped; the vulnerability occurs because the rejection signal is not honored in all code paths. This affects the tarfile module's extractall() method with custom filter functions on systems without link support.
Affected products
- Python CPython 3.12, 3.13
Timeline
- 2026-09-11: disclosed
- 2026-09-11: patched