CVE-2026-114583: tar filter allows writing outside destination via empty-named symlink

Published Oct 22, 2026
·
Updated

tar filter allows writing outside destination via empty-named symlink

Other sources

tarfile.tarfilter 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.tarfilter counterpart of CVE-2026-7774, which covered tarfile.datafilter.

— Ubuntu

Affected Software

51 affected componentsFixes available
Python Software Foundation CPython
All of the following
azurelinux/python3<3.12.16-1
3.12.16-1
Microsoft Azure Linux=3.0
ubuntu/python2.7*
ubuntu/python3.4*
ubuntu/python3.5*
ubuntu/python2.7*
ubuntu/python3.5*
ubuntu/python2.7*
ubuntu/python3.6*
ubuntu/python3.7*
ubuntu/python3.8*
ubuntu/python2.7*
ubuntu/python3.9*
ubuntu/python3.10*
ubuntu/python2.7*
ubuntu/python3.11*
ubuntu/python3.12*
ubuntu/python3.14*
ubuntu/python3.14*
bitnami/libpython<3.11.18
3.11.18
bitnami/libpython>=3.12.0<3.12.16
3.12.16
bitnami/libpython>=3.13.0<3.13.18
3.13.18
bitnami/libpython>=3.14.0<3.14.10
3.14.10
bitnami/libpython>=3.15.0<3.15.2
3.15.2
bitnami/python-min<3.11.18
3.11.18
bitnami/python-min>=3.12.0<3.12.16
3.12.16
bitnami/python-min>=3.13.0<3.13.18
3.13.18
bitnami/python-min>=3.14.0<3.14.10
3.14.10
bitnami/python-min>=3.15.0<3.15.2
3.15.2
bitnami/python<3.11.18
3.11.18
bitnami/python>=3.12.0<3.12.16
3.12.16
bitnami/python>=3.13.0<3.13.18
3.13.18
bitnami/python>=3.14.0<3.14.10
3.14.10
bitnami/python>=3.15.0<3.15.2
3.15.2
debian/jython*
debian/jython*
debian/jython*
debian/pypy3*
debian/pypy3*
debian/pypy3*
debian/python3.11*
debian/python3.13*
debian/python3.14<3.14.9-1
3.14.9-1
debian/python3.15<3.15.1-1
3.15.1-1
debian/jython<=2.7.3+repack1-1
debian/pypy3<=7.3.11+dfsg-2+deb12u3, <=7.3.19+dfsg-2, <=8.0.1+dfsg-1
debian/python3.11<=3.11.2-6+deb12u8, <=3.11.2-6+deb12u9
debian/python3.13<=3.13.5-2+deb13u5
3.13.18-1
debian/python3.14
3.14.10-1
debian/python3.15
3.15.2-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade azurelinux/python3 to a version that resolves this vulnerability.

    Fixed in 3.12.16-1
  2. Upgrade

    Upgrade bitnami/libpython to a version that resolves this vulnerability.

    Fixed in 3.11.18
  3. Upgrade

    Upgrade bitnami/libpython to a version that resolves this vulnerability.

    Fixed in 3.12.16
  4. Upgrade

    Upgrade bitnami/libpython to a version that resolves this vulnerability.

    Fixed in 3.13.18
  5. Upgrade

    Upgrade bitnami/libpython to a version that resolves this vulnerability.

    Fixed in 3.14.10
  6. Upgrade

    Upgrade bitnami/libpython to a version that resolves this vulnerability.

    Fixed in 3.15.2
  7. Upgrade

    Upgrade bitnami/python-min to a version that resolves this vulnerability.

    Fixed in 3.11.18
  8. Upgrade

    Upgrade bitnami/python-min to a version that resolves this vulnerability.

    Fixed in 3.12.16
  9. Upgrade

    Upgrade bitnami/python-min to a version that resolves this vulnerability.

    Fixed in 3.13.18
  10. Upgrade

    Upgrade bitnami/python-min to a version that resolves this vulnerability.

    Fixed in 3.14.10
  11. Upgrade

    Upgrade bitnami/python-min to a version that resolves this vulnerability.

    Fixed in 3.15.2
  12. Upgrade

    Upgrade bitnami/python to a version that resolves this vulnerability.

    Fixed in 3.11.18
  13. Upgrade

    Upgrade bitnami/python to a version that resolves this vulnerability.

    Fixed in 3.12.16
  14. Upgrade

    Upgrade bitnami/python to a version that resolves this vulnerability.

    Fixed in 3.13.18
  15. Upgrade

    Upgrade bitnami/python to a version that resolves this vulnerability.

    Fixed in 3.14.10
  16. Upgrade

    Upgrade bitnami/python to a version that resolves this vulnerability.

    Fixed in 3.15.2
  17. Upgrade

    Upgrade debian/python3.13 to a version that resolves this vulnerability.

    Fixed in 3.13.18-1
  18. Upgrade

    Upgrade debian/python3.14 to a version that resolves this vulnerability.

    Fixed in 3.14.10-1
  19. Upgrade

    Upgrade debian/python3.15 to a version that resolves this vulnerability.

    Fixed in 3.15.2-1
  20. Upgrade

    Upgrade debian/python3.14 to a version that resolves this vulnerability.

    Fixed in 3.14.9-1
  21. Upgrade

    Upgrade debian/python3.15 to a version that resolves this vulnerability.

    Fixed in 3.15.1-1

Event History

Oct 22, 2026
CVE Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
RemedyDescriptionSeverityAffected Software
CVE Published
via MITRE·08:57 PM
Advisory Published
via OSV·08:57 PM
Data Sourced
via MITRE·08:57 PM
Description
Data Sourced
via OSV·08:57 PM
Severity
Data Sourced
via NVD·09:17 PM
DescriptionSeverityWeakness
Oct 24, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeaknessAffected Software
Oct 28, 2026
Data Sourced
via OSV·08:17 PM
Affected Software

Frequently Asked Questions

1

Who is exposed to this issue?

Applications that extract untrusted or attacker-controlled tar archives with tarfile.extractall() using filter="tar" are exposed. The impact is limited by the permissions of the process performing extraction.

2

What does an attacker need to exploit it?

An attacker needs to supply a crafted tar archive containing link entries, such as symlinks with empty or directory-like names, followed by archive members whose extraction can be redirected through those links.

3

Are extra application settings required for exploitation?

The affected extraction mode is explicitly filter="tar". Exploitation occurs when the application extracts a malicious archive using that filter; no other configuration requirements are provided.

4

What is the practical impact of successful exploitation?

A crafted archive can cause later members to be written outside the intended destination directory. The attacker can write only where the extracting process has permission.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203