CVE-2025-8869 Affecting python-pip package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIANUNSTABLE-PYTHONPIP-13045608
  • published25 Sept 2025
  • disclosed24 Sept 2025

Introduced: 24 Sep 2025

NewCVE-2025-8869  (opens in a new tab)

How to fix?

There is no fixed version for Debian:unstable python-pip.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-pip package and not the python-pip package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1