CVE-2025-8869
Last modified
CVE-2025-8869 is a medium-severity vulnerability rated 5.9/10 on the CVSS scale. When extracting a tar archive pip may not check symbolic links point into the extraction directory if the tarfile module doesn't implement PEP 706. Note that upgrading pip to a "fixed" version for this vulnerability doesn't fix all known vulnerabilities that are remediated by using a Python version that implements PEP 706. Note that this is a vulnerability in pip's fallback implementation of tar extraction for Python versions that don't implement PEP 706 and therefore are not secure to all vulnerabilities in the Python 'tarfile' module. If you're using a Python version that implements PEP 706 then pip doesn't use the "vulnerable" fallback code. Mitigations include upgrading to a version of pip that includes the fix, upgrading to a Python version that implements PEP 706 (Python >=3.9.17, >=3.10.12, >=3.11.4, or >=3.12), applying the linked patch, or inspecting source distributions (sdists) before installation as is already a best-practice.. EPSS estimates a 0.44% chance of exploitation in the next 30 days.
Description
When extracting a tar archive pip may not check symbolic links point into the extraction directory if the tarfile module doesn't implement PEP 706. Note that upgrading pip to a "fixed" version for this vulnerability doesn't fix all known vulnerabilities that are remediated by using a Python version that implements PEP 706. Note that this is a vulnerability in pip's fallback implementation of tar extraction for Python versions that don't implement PEP 706 and therefore are not secure to all vulnerabilities in the Python 'tarfile' module. If you're using a Python version that implements PEP 706 then pip doesn't use the "vulnerable" fallback code. Mitigations include upgrading to a version of pip that includes the fix, upgrading to a Python version that implements PEP 706 (Python >=3.9.17, >=3.10.12, >=3.11.4, or >=3.12), applying the linked patch, or inspecting source distributions (sdists) before installation as is already a best-practice.
Metrics
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2025-8869?
How severe is CVE-2025-8869?
How do I fix CVE-2025-8869?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-8863YugabyteDB diagnostic information was transmitted over HTTP,…7
- CVE-2025-8864Shared Access Signature token is not masked in the backup co…6.8
- CVE-2025-8865The YugabyteDB tablet server contains a flaw in its YCQL que…4.1
- CVE-2025-8866YugabyteDB Anywhere web server does not properly enforce aut…5.1
- CVE-2025-8867The Graphina - Elementor Charts and Graphs plugin for WordPr…6.4
- CVE-2025-8868In Progress Chef Automate, versions earlier than 4.13.295, o…8.8
- CVE-2025-8870On affected platforms running Arista EOS, certain serial con…5.6
- CVE-2025-8871The Everest Forms (Pro) plugin for WordPress is vulnerable t…5.6
- CVE-2025-8872On affected platforms running Arista EOS with OSPFv3 configu…7.1
- CVE-2025-8873On affected platforms running Arista EOS with IPsec configur…8.7
- CVE-2025-8874The Master Addons – Elementor Addons with White Label, Free …6.4
- CVE-2025-8875Deserialization of Untrusted Data vulnerability in N-able N-…7.8
Are you affected by CVE-2025-8869?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
