# CVE-2026-19672: tarfile extraction filter bypass allows creation of directories outside the destination

> Attackers can create empty directories outside the extraction destination via crafted tar archives, potentially disrupting filesystem structure.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** ALPINE-CVE-2026-19672, AZL-110510, AZL-97038, BELL-CVE-2026-19672, BIT-libpython-2026-19672, BIT-python-2026-19672, BIT-python-min-2026-19672, DEBIAN-CVE-2026-19672, ECHO-85b0-6a57-a5e5, GHSA-prxg-vvhf-mgqq, MINI-4j2f-xmj7-f2pw, MINI-f3m3-jmm4-4v57, MINI-g45v-4wv4-fjpj, MINI-p789-r3r4-8gwh, MINI-r3v9-jr7p-qq28, PSF-2026-38, UBUNTU-CVE-2026-19672

## What is CVE-2026-19672?

CVE-2026-19672 is a medium-severity path traversal vulnerability in CPython, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The tarfile module's tar and data
 extraction filters created directories outside the destination for 
members whose name leaves the destination and returns to it, such as ../evil/../dest/sub/file. The containment check used the resolved path, but intermediate directories were created from the name as given.

Only
 empty directories are created outside the destination. Member contents 
are still extracted inside it. To return to the destination the member's
 name must contain the destination directory's own final component, so 
extraction into a secure randomised directory is not affected.

This affects POSIX platforms only. On Windows, .. components are collapsed before the path reaches the filesystem, so the directories outside the destination are never created.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-19672?

3 open source packages ship an affected version, including libpython, python and python-min.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libpython` | Bitnami | All versions | 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8 |
| `python` | Bitnami | All versions | 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8 |
| `python-min` | Bitnami | All versions | 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8 |

## How do I fix CVE-2026-19672?

Upgrade libpython to a fixed version for your release line: 3.10.22, 3.11.17, 3.12.15 or 3.13.16.

## Is CVE-2026-19672 being exploited?

There is no known exploitation of CVE-2026-19672 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19672 and fix it if it is affected.

What it is: CVE-2026-19672 is a medium-severity path traversal vulnerability in CPython, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19672 in the wild and no public exploit code.

Affected packages and fixed versions:
- libpython (Bitnami): affected all versions; fixed in 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8
- python (Bitnami): affected all versions; fixed in 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8
- python-min (Bitnami): affected all versions; fixed in 3.10.22, 3.11.17, 3.12.15, 3.13.16, 3.14.8

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19672/ (Markdown: https://insights.sbomify.com/CVE-2026-19672/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19672
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19672
- OSV: https://osv.dev/vulnerability/CVE-2026-19672

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19672/
Summaries are generated and may contain mistakes; the official description above is the record.