Live › vulnerability › CVE-2026-114583
Go to dashboardA crafted tar archive with malicious link entries, including symlinks with empty or directory-like names, can make later members land outside the extraction directory when code calls tarfile.extractall() with filter="tar". The attacker gets file writes outside the destination, limited by the permissions of the extracting process.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Applications running Python that call tarfile.extractall() with filter="tar" on archives an outside party can supply, such as user uploads or downloaded packages. Code that extracts only trusted archives, or that does not use the tar filter, is less exposed. The sources do not say which Python versions are affected.
No product ranges from the sources yet.
python3 --version and compare against the patched release named in the Python advisory (the sources do not give the fixed version).extractall( and filter="tar" to find code that extracts archives with this filter.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
tarfile.tar_filter could be bypassed using crafted link entries, including symlinks with empty or directory-like names, to redirect later archive members outside the intended extraction directory. This allowed a malicious tar archive to cause tarfile.extractall() with filter="tar" to write files outside the destination directory, subject to the permissions of the extracting process.
This is the tarfile.tar_filter counterpart of CVE-2026-7774, which covered tarfile.data_filter.
This page as .md · .json · in your agent: get_signal("CVE-2026-114583")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.