# CVE-2026-102925: virtualenv bash and fish activation scripts execute commands embedded in paths

> Attackers can execute arbitrary commands with user privileges by crafting virtual environment paths that exploit quoting flaws in activation scripts.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** AZL-105675, BIT-virtualenv-2026-102925, DEBIAN-CVE-2026-102925, ECHO-6eef-2a90-03f8, GHSA-p58f-9548-mpm2, MINI-c68v-88m6-f83w, MINI-q3wr-973g-xxfh, PYSEC-2026-4013, ROOT-APP-PYPI-CVE-2026-102925, UBUNTU-CVE-2026-102925

## What is CVE-2026-102925?

CVE-2026-102925 is a high-severity command injection vulnerability in pypa virtualenv, published on 29 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

virtualenv is a tool for creating isolated virtual python environments. Prior to 21.7.13, the generated activate (bash and zsh) and activate.fish scripts place values already escaped by shlex.quote inside an additional quoted context. In the bash and zsh script, a crafted virtual environment path reaches __VIRTUAL_ENV__ when a relocated environment's recorded directory is absent; in the fish script, crafted Tcl or Tk library paths reach __TCL_LIBRARY__ or __TK_LIBRARY__. The surplus quotes can terminate the data-only quoted run and leave shell metacharacters parsed as commands when a user sources the activation script, allowing code execution with that user's privileges. This issue is fixed in version 21.7.13.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

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


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

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

Upgrade virtualenv to 21.7.13 or later.

## Is CVE-2026-102925 being exploited?

There is no known exploitation of CVE-2026-102925 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102925 is a high-severity command injection vulnerability in pypa virtualenv, published on 29 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-102925 in the wild and no public exploit code.

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

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-102925/ (Markdown: https://insights.sbomify.com/CVE-2026-102925/index.md)
```

## Sources

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

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