# uv vulnerable to arbitrary file deletion through RECORD entries

Advisory record · `GHSA-pjjw-68hj-v9mw`

- **Identifiers:** `GHSA-pjjw-68hj-v9mw` · `CVE-2026-114110`
- **State:** Confirmed
- **Severity:** CVSS 8.7 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-23](https://cwe.mitre.org/data/definitions/23.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 10 Apr 2026
- **Updated:** 23 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Apr 2026, 19:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `uv` (PyPI): affected `<0.11.6`; fixed in `0.11.6`

## Machine-written summary

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

> uv versions before 0.11.6 are vulnerable to arbitrary file deletion through malformed RECORD entries in Python wheels. A user must install and then uninstall a crafted wheel, which can cause files outside the installation prefix to be deleted; the source notes that only files, not directories, can be removed. Upgrade to uv 0.11.6 or newer, which ignores RECORD paths that escape the installation prefix on uninstall.

Written 1 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

- 8.7 High, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0035, the 28th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:08 UTC: First seen by agentprime
- 31 Oct 2026, 14:08 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pjjw-68hj-v9mw)

## Sources

- [GitHub Advisory Database: GHSA-pjjw-68hj-v9mw](https://github.com/advisories/GHSA-pjjw-68hj-v9mw)
- [OSV: GHSA-pjjw-68hj-v9mw](https://osv.dev/vulnerability/GHSA-pjjw-68hj-v9mw)
- <https://github.com/astral-sh/uv/security/advisories/GHSA-pjjw-68hj-v9mw>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-114110>
- <https://github.com/astral-sh/uv/pull/18942>
- <https://github.com/astral-sh/uv/pull/18943>
- <https://github.com/astral-sh/uv/commit/7983c7a5bef236fd8a04580fcedae7bd5bde4cdb>
- <https://github.com/astral-sh/uv/commit/a0e461ac44851f9a0f6e8974733e77d46f7a9ea9>
- <https://github.com/astral-sh/uv>
- <https://github.com/astral-sh/uv/releases/tag/0.11.6>
- <https://www.vulncheck.com/advisories/astral-uv-before-0.11.6-arbitrary-file-deletion-via-wheel-record-entries>

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-pjjw-68hj-v9mw>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pjjw-68hj-v9mw/>. Everything for agents: <https://agentprime.io/llms.txt>.
