Extraction-directory escape in Python tarfile.tar_filter
CVE-2026-114583 is an extraction-filter bypass in CPython's tarfile.tar_filter. Crafted tar archive link entries, including symbolic links with empty or directory-like names, can redirect subsequent archive members outside the intended extraction directory. Applications calling tarfile.extractall() with filter="tar" can consequently write files outside the destination, subject to the extracting process's filesystem permissions. This vulnerability is the tar_filter counterpart of CVE-2026-7774, which affected tarfile.data_filter.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
An attacker-controlled archive can cause unauthorized creation or overwriting of files outside the extraction destination, compromising filesystem integrity within the extracting process's writable scope. The extraction filter does not provide the expected directory-containment guarantee.
If you can’t patch tonight, do this now.
Until patched, avoid extracting untrusted tar archives with filter="tar". If extraction is unavoidable, perform it in a disposable sandbox with minimal filesystem access and least-privileged credentials. Do not rely on the extraction destination directory alone to contain malicious archive writes.
Patch, then assume compromise.
Upgrade to a release incorporating the CPython fix: Python 3.15.2, 3.14.10, 3.13.18, 3.12.16, or 3.11.18, or a subsequent release on the corresponding branch. Alternatively, apply the appropriate branch-specific security patch. The corrected tar_filter rejects link entries that replace the extraction destination directory itself. For distribution-managed Python installations, confirm that the installed package incorporates the fix; upstream release availability does not establish that every distribution package has been patched.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.