CVE-2026-113725 json
virtualenv bash activate runs commands from an environment name with a backslash before $
published 20d ago modified 11d ago also BIT-virtualenv-2026-113725 , EUVD-2026-105273 , GHSA-vxj4-q4g9-crj7
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 18%
- public exploits
- 0
- none known
Summary
virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.7, the bash activate script escapes the environment name for only one of the two passes bash makes over PS1, so a backslash in the name undoes the escaping and a name containing \$(...) runs as commands in the user's shell each time bash draws the prompt. This issue is fixed in version 21.14.7.
Patch / fix
- pypi virtualenv 21.14.7
- bitnami virtualenv 21.14.7
- virtualenv virtualenv 21.14.7
- python-virtualenv Azure Linux 3.0 20.36.1-10
azure linux advisories AZL-110115
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
Is CVE-2026-113725 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-113725 updated cvss 7.8
virtualenv: virtualenv: arbitrary code execution via crafted environment name
-
Red Hat OpenShift Lightspeed openshift-lightspeed/lightspeed-service-api-rhel9affected: workaround, no fix planned “Will not fix”
-
Red Hat Ansible Automation Platform 2 python-virtualenv 20.25.1-2.el10ap, python3.12-virtualenv 20.25.1-2.el9ap, ansible-automation-platform-26/controller-rhel9, ansible-automation-platform-27/controller-rhel9, ansible-automation-platform-26/lightspeed-chatbot-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-ta-lmes-job-rhel9, rhoai/odh-feature-server-rhel9, rhai-early-access/docling-serve-cuda-rhel9, rhoai/odh-kserve-storage-initializer-rhel9, rhoai/odh-trustyai-nemo-guardrails-server-rhel9, rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9, +2 more Red Hat OpenShift Dev Spaces devspaces/udi-rhel9 Red Hat Satellite 6 satellite/iop-yuptoo-rhel9, satellite/iop-host-inventory-rhel9, satellite/iop-advisor-backend-rhel9affected: workaround, no fix available
-
Red Hat Ansible Automation Platform 2 python3.11-virtualenv 20.25.1-1.el9ap, ansible-automation-platform-26/eda-controller-rhel9, ansible-automation-platform-27/eda-controller-rhel9not affected: vulnerable code not present
-
Red Hat OpenShift AI (RHOAI) rhoai/odh-kserve-agent-rhel9, rhoai/odh-kserve-router-rhel9, rhoai/odh-kserve-controller-rhel9, rhoai/odh-training-rocm64-torch28-py312-rhel9 Red Hat OpenShift Container Platform 4 python-virtualenv 20.25.1-2.el10apnot affected: component not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 19d ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | virtualenv | <21.14.7 |
21.14.7 |
| bitnami | virtualenv | <21.14.7 |
21.14.7 |
Affected products
- pypa virtualenv
Classification
References
Sources
- CVE List CVE-2026-113725
- GitHub Advisory GHSA-vxj4-q4g9-crj7
- NVD CVE-2026-113725
- OSV BIT-virtualenv-2026-113725
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.