CVE-2026-113722

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-10-21. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-105304 (ENISA EUVD) · GHSA-c978-59m8-c77v (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, virtualenv's ScriptMakerCustom and pip pass an incompletely quoted interpreter path to distlib ScriptMaker when generating POSIX console scripts. When the path contains a space or produces a shebang longer than 127 bytes, distlib emits a /bin/sh wrapper whose double-quoted interpreter path still expands command substitutions and backticks. An attacker who influences the environment destination can therefore execute commands with the user's privileges when the user later runs a generated launcher; environment creation and activation do not trigger the command. Existing launchers are not repaired by upgrading virtualenv alone and must be regenerated, while a later independent pip installation or upgrade can reintroduce an affected launcher because pip's vendored distlib is unchanged. The virtualenv fix is released in version 21.14.9.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
51
EG Risk 51/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 20, 2026

Last Modified

October 23, 2026

Advisory Details (4)

Auto-updated Oct 20, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Generated POSIX console launchers interpret destination paths as shell syntax · Advisory · pypa/virtualenv · GitHub

Affected: 21.14.9.

https://github.com/pypa/virtualenv/security/advisories/GHSA-c978-59m8-c77v
GitHub release Patch Available

21.14.9

Patch available: pypa/virtualenv 21.14.9

https://github.com/pypa/virtualenv/releases/tag/21.14.9
GitHub pull request

🐛 fix(seed): preserve interpreter paths in console scripts

Fix merged in pypa/virtualenv PR #3417 on 2026-10-17 — awaiting tagged release

https://github.com/pypa/virtualenv/pull/3417
GitHub commit

commit 2519941bed33 (pypa/virtualenv)

Fix landed in pypa/virtualenv commit 2519941bed33 — awaiting tagged release

https://github.com/pypa/virtualenv/commit/2519941bed33ee0d3ac99277f67913e439e476a9

Vendor Advisories for CVE-2026-113722(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipvirtualenv @ 21.14.9 (fixes < 21.14.9)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
virtualenv0.8 ... 21.9.1 (304 versions)
  • every version up to 21.14.9: fixed in 21.14.9
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 22× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  2. 2026-11-01 07:59 UTCGHSA enrichmentGHSA-c978-59m8-c77v · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-11-01 07:59 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  5. 2026-10-30 17:55 UTCEG score recompute
  6. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  8. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  10. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  11. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-10-25 14:51 UTCEG score recompute
  13. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-23 02:25 UTCEG score recompute
  16. 2026-10-23 02:07 UTCEG score recompute
  17. 2026-10-22 17:06 UTCEG score recompute
  18. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-10-20 20:26 UTCEG score recompute
  21. 2026-10-20 19:57 UTCEG score recomputeFirst assessed: 7.8 HIGH
  22. 2026-10-20 19:56 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-113722?
CVE-2026-113722 is a high-severity vulnerability; its CVE record was published on October 20, 2026. virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, virtualenv's ScriptMakerCustom and pip pass an incompletely quoted interpreter path to distlib ScriptMaker when generating POSIX console scripts. When the path contains a space or produces a shebang longer…
When was the CVE record for CVE-2026-113722 published?
The CVE record for CVE-2026-113722 was published on October 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-113722 actively exploited?
CVE-2026-113722 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-113722?
CVE-2026-113722 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-113722?
A fix for CVE-2026-113722 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-113722 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-113722

Explore →

Is Your Infrastructure Affected by CVE-2026-113722?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs