CVE-2026-3219: pip has an interpretation conflict due to handling both concatenated tar and ZIP files as ZIP files
pip handles concatenated tar and ZIP files as ZIP files regardless of filename or whether a file is both a tar and ZIP file. This behavior could result in confusing installation behavior, such as installing "incorrect" files according to the filename of the archive. New behavior only proceeds with installation if the file identifies uniquely as a ZIP or tar archive, not as both.
Published Apr 20, 2026 · Updated May 20, 2026
Affected packages
pip
- Ecosystem
- PyPI
- Affected
- <= 26.0.1
- Fixed in
- 26.1
- Check
pip show pip
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
pip handles concatenated tar and ZIP files as ZIP files regardless of filename or whether a file is both a tar and ZIP file. This behavior could result in confusing installation behavior, such as installing "incorrect" files according to the filename of the archive. New behavior only proceeds with installation if the file identifies uniquely as a ZIP or tar archive, not as both.
Credited to amine-malloul-gira, tsokalski.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-13346
pip would incorrectly handle doubly-encoded package URLs from indexes
medium5.6Jul 29, 2026CVE-2026-8643
pip: Path traversal in console_scripts/gui_scripts entry point names allows installing scripts outside of target directory
medium8.0Jun 1, 2026CVE-2026-6357
pip Vulnerable to Inclusion of Functionality from Untrusted Control Sphere
medium5.3Apr 27, 2026CVE-2026-1703
pip Path Traversal vulnerability
low2.0Feb 2, 2026CVE-2025-8869
pip's fallback tar extraction doesn't check symbolic links point to extraction directory
medium5.9Sep 24, 2025
