Skip to content
Fencer Intel
high 7.1

CVE-2026-113718 json

virtualenv: Xonsh activation literals depend on the script decoding codec

published 20d ago modified 11d ago also BIT-virtualenv-2026-113718 , EUVD-2026-105299 , GHSA-394h-qwmc-48pf

cvss
7.1
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 15%
public exploits
0
none known

Summary

virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, POSIX xonsh activation quote() uses repr() to write printable non-ASCII prompt or destination data into UTF-8 activate.xsh, while xonsh can read that script using $XONSH_ENCODING. Under a legacy multibyte codec such as GBK or Big5, a UTF-8 trail byte can consume the backslash before an adjacent quote, allowing the literal to close and attacker-influenced statements to execute when the user sources the generated script. This issue is fixed in version 21.14.9.

Patch / fix

  • pypi virtualenv 21.14.9
  • bitnami virtualenv 21.14.9
  • virtualenv virtualenv 21.14.9
  • python-virtualenv openSUSE Tumbleweed 21.15.1-1.1

opensuse advisories openSUSE-SU-2026:12372-1

Is CVE-2026-113718 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 Fencer

Vendor 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-113718 updated cvss 7.0

virtualenv: virtualenv: arbitrary code execution via improper quoting in xonsh activation scripts

  • Red Hat OpenShift Lightspeed openshift-lightspeed/lightspeed-service-api-rhel9
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Ansible Automation Platform 2 python-virtualenv 20.25.1-2.el10ap, python3.11-virtualenv 20.25.1-1.el9ap, 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-training-rocm64-torch28-py312-rhel9, rhoai/odh-trustyai-nemo-guardrails-server-rhel9, +3 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-rhel9
    affected: workaround, no fix available
  • Red Hat Ansible Automation Platform 2 ansible-automation-platform-26/eda-controller-rhel9, ansible-automation-platform-27/eda-controller-rhel9
    not 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 Red Hat OpenShift Container Platform 4 python-virtualenv 20.25.1-2.el10ap
    not 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
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
13d ago

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/pypa/virtualenv/security/advisories/GHSA-394h-qwmc-48pf referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 7.1 CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA 4.0 7.1 CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
pypi virtualenv
<21.14.9
21.14.9
bitnami virtualenv
<21.14.9
21.14.9

Affected products

  • pypa virtualenv

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

References

Sources

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.