# CVE-2026-113719: virtualenv: Seed replacement does not contain metadata deletion paths


- **Severity:** Medium 4.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** AZL-110121, BIT-virtualenv-2026-113719, DEBIAN-CVE-2026-113719, ECHO-b0db-7316-fd96, GHSA-hhxq-47xx-j5xx, MINI-h9fw-3f73-rhrc, UBUNTU-CVE-2026-113719

## What is CVE-2026-113719?

CVE-2026-113719 is a medium-severity vulnerability in pypa virtualenv, published on 20 Oct 2026. 

### Official description

virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, PipInstall._uninstall_previous_version() accepts existing seed-package metadata and _uninstall_dist() joins entries from top_level.txt and RECORD to site-packages without checking containment. When a reused destination contains distribution metadata influenced by another account, relative traversal, absolute entries, or linked parents can cause app-data reseeding to delete files outside the environment or the environment root with the invoking user's permissions, provided that user has deletion rights over the named paths. The deletion occurs during environment creation before any later use of the environment. Fresh environments without existing package metadata and creation with --clear do not enter this cleanup path. This issue is fixed in version 21.14.9.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-113719?

3 open source packages ship an affected version, including virtualenv.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `virtualenv` | Bitnami | All versions | 21.14.9 |
| `virtualenv` | PyPI | All versions | 21.14.9 |
| `virtualenv` | PyPI | All versions | 21.14.9 |

## How do I fix CVE-2026-113719?

Upgrade virtualenv to 21.14.9 or later.

## Is CVE-2026-113719 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113719 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-113719 and fix it if it is affected.

What it is: CVE-2026-113719 is a medium-severity vulnerability in pypa virtualenv, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113719 exists.

Affected packages and fixed versions:
- virtualenv (Bitnami): affected all versions; fixed in 21.14.9
- virtualenv (PyPI): affected all versions; fixed in 21.14.9
- virtualenv (PyPI): affected all versions; fixed in 21.14.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-113719/ (Markdown: https://insights.sbomify.com/CVE-2026-113719/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-113719
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-113719
- OSV: https://osv.dev/vulnerability/CVE-2026-113719

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-113719/
Summaries are generated and may contain mistakes; the official description above is the record.