# pip's fallback tar extraction doesn't check symbolic links point to extraction directory

Advisory record · `GHSA-4xh5-x5gv-qwph`

- **Identifiers:** `GHSA-4xh5-x5gv-qwph` · `CVE-2025-8869` · `PYSEC-2026-1795`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-59](https://cwe.mitre.org/data/definitions/59.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 24 Sept 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 24 Sept 2025, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `pip` (PyPI): affected `<25.3`; fixed in `25.3`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Pip versions before 25.3 may not check that symbolic links in tar archives point into the extraction directory when running on Python versions that lack PEP 706 support, because pip then uses its own fallback tar extraction code. An attacker who can get a user to install a malicious source distribution could cause files to be written outside the intended directory. Upgrade pip to version 25.3 or later, or use a Python version that implements PEP 706 (3.9.17, 3.10.12, 3.11.4, or 3.12 and later), which avoids the fallback code.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.9 Medium, CVSS 4.0: `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`, from CNA (PSF)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0049, the 42nd percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:34 UTC: First seen by agentprime
- 31 Oct 2026, 14:34 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-4xh5-x5gv-qwph)

## Sources

- [GitHub Advisory Database: GHSA-4xh5-x5gv-qwph](https://github.com/advisories/GHSA-4xh5-x5gv-qwph)
- [OSV: GHSA-4xh5-x5gv-qwph](https://osv.dev/vulnerability/GHSA-4xh5-x5gv-qwph)
- <https://nvd.nist.gov/vuln/detail/CVE-2025-8869>
- <https://github.com/pypa/pip/pull/13550>
- <https://github.com/pypa/pip/commit/f2b92314da012b9fffa36b3f3e67748a37ef464a>
- <https://github.com/pypa/pip>
- <https://lists.debian.org/debian-lts-announce/2025/10/msg00028.html>
- <https://mail.python.org/archives/list/security-announce@python.org/thread/IF5A3GCJY3VH7BVHJKOWOJFKTW7VFQEN>
- <https://pip.pypa.io/en/stable/news/#v25-2>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-4xh5-x5gv-qwph>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-4xh5-x5gv-qwph/>. Everything for agents: <https://agentprime.io/llms.txt>.
