CVE-2026-102938

MEDIUMPre-NVD 5.85.8
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-89465 (ENISA EUVD) · GHSA-9h9j-4vrj-gf7g (GitHub Security Advisories)Source: ENISA EUVD

5.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

virtualenv is a tool for creating isolated virtual python environments. Prior to 21.7.11, PyEnvCfg.write() writes prompt values verbatim to the line-oriented pyvenv.cfg format while PyEnvCfg._read_values() parses the file with str.splitlines() and accepts the last value for duplicate keys. An attacker who influences --prompt, VIRTUALENV_PROMPT, or configuration input can insert a recognized line boundary and additional keys, including home, causing consumers to use an attacker-selected base interpreter or corrupted environment metadata. The security impact requires prompt input from outside the operator's trust boundary; directly supplied prompt content primarily corrupts the operator's own environment. This issue is fixed in version 21.7.11.

CVSS v3
5.8
EG Score
5.8MEDIUMmedium confidence
EG Risk
26
EG Risk 26/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)
Severity58% × 45%
Impact severity (EG Severity): CVSS 5.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.1%
EPSS %ILE
3rd
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 (5.8): severity, escalated by confirmed exploitation. This CVE's 5.8 is its impact severity (EG Severity), not escalated.

EG Severity
5.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.1% 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

September 29, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 29, 2026
Patch available. Sources: github_pr, github_commit, github_release, github.
GitHub release Patch Available

21.7.11

Patch available: pypa/virtualenv 21.7.11

https://github.com/pypa/virtualenv/releases/tag/21.7.11
GitHub commit Patch Available

commit a30f99546104 (pypa/virtualenv)

Patch available: pypa/virtualenv 21.7.11 (contains commit a30f99546104)

https://github.com/pypa/virtualenv/commit/a30f995461043acb6cacbf3a890951563ccf7140
GitHub pull request Patch Available

🐛 fix(create): keep pyvenv.cfg values on a single line

Patch available: pypa/virtualenv 21.7.11 (PR #3247 merged 2026-09-17)

https://github.com/pypa/virtualenv/pull/3247
GitHub advisoryMentions a patch (unverified)

virtualenv writes prompt values into pyvenv.cfg without sanitizing line boundaries, allowing configuration injection · Advisory · pypa/virtualenv · GitHub

https://github.com/pypa/virtualenv/security/advisories/GHSA-9h9j-4vrj-gf7g

Vendor Advisories for CVE-2026-102938(7)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatansible-automation-platform-27/eda-controller-rhel9:17921410102026-10-21redhat
redhatrhoai/odh-ta-lmes-job-rhel9:17915535272026-10-21redhat
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17918254692026-10-21redhat
redhatansible-automation-platform-26/lightspeed-chatbot-rhel9:17919787982026-10-21redhat
redhatrhoai/odh-trustyai-nemo-guardrails-server-rhel9:17915561282026-10-19redhat
pipvirtualenv @ 21.7.11 (fixes <= 21.7.10)—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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-virtualenv20.17.1+ds-1 ... 21.5.1+ds-1 (33 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-virtualenv20.31.2+ds-1 ... 21.5.1+ds-1 (13 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-virtualenv20.31.2+ds-1 ... 21.5.1+ds-1 (12 versions)
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
virtualenv0.8 ... 21.7.9 (280 versions)
  • every version up to 21.7.11: fixed in 21.7.11
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 57× 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.1% · 3rd percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-9h9j-4vrj-gf7g · GitHub severity MODERATE
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-29 14:49 UTCEG score recompute
  8. 2026-10-29 14:49 UTCVendor advisory
  9. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  13. 2026-10-25 14:56 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-23 09:27 UTCEG score recompute
  17. 2026-10-23 09:27 UTCVendor advisory
  18. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  19. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  20. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-10-18 05:10 UTCEG score recompute
  24. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  25. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
Show 41 more
  1. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-12 16:40 UTCEG score recompute
  5. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-11 22:26 UTCVendor advisory
  7. 2026-10-11 20:15 UTCEG score recompute
  8. 2026-10-11 18:28 UTCEG score recompute
  9. 2026-10-11 15:01 UTCEG score recompute
  10. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-11 00:17 UTCEG score recompute
  12. 2026-10-11 00:17 UTCVendor advisory
  13. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-10 02:05 UTCEG score recompute
  15. 2026-10-10 02:05 UTCVendor advisory
  16. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-09 03:53 UTCEG score recompute
  18. 2026-10-09 03:53 UTCVendor advisory
  19. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-08 05:43 UTCEG score recompute
  21. 2026-10-08 05:43 UTCVendor advisory
  22. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-07 07:33 UTCEG score recompute
  24. 2026-10-07 07:33 UTCVendor advisory
  25. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-10-06 09:23 UTCEG score recompute
  27. 2026-10-06 09:23 UTCVendor advisory
  28. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-10-05 11:15 UTCEG score recompute
  30. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-10-03 14:52 UTCEG score recompute
  32. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  33. 2026-10-02 16:43 UTCEG score recompute
  34. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  35. 2026-09-30 20:23 UTCEG score recompute
  36. 2026-09-30 19:56 UTCEG score recompute
  37. 2026-09-30 19:30 UTCEG score recompute
  38. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-09-29 21:21 UTCEG score recompute
  40. 2026-09-29 21:05 UTCEG score recomputeFirst assessed: 5.8 MEDIUM
  41. 2026-09-29 21:03 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-102938?
CVE-2026-102938 is a medium-severity vulnerability; its CVE record was published on September 29, 2026. virtualenv is a tool for creating isolated virtual python environments. Prior to 21.7.11, PyEnvCfg.write() writes prompt values verbatim to the line-oriented pyvenv.cfg format while PyEnvCfg._read_values() parses the file with str.splitlines() and accepts the last value for duplicate keys. An…
When was the CVE record for CVE-2026-102938 published?
The CVE record for CVE-2026-102938 was published on September 29, 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 September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-102938 actively exploited?
CVE-2026-102938 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102938?
CVE-2026-102938 has a CVSS base score of 5.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102938?
A fix for CVE-2026-102938 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102938 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-102938

Explore →

Is Your Infrastructure Affected by CVE-2026-102938?

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

Book a Demo →Browse All CVEs