CVE-2026-85013

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (11th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.3Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

A flaw was found in environment-modules. A local attacker can exploit this vulnerability by placing a maliciously named modulefile in a location visible to the victim's MODULEPATH. When the victim uses Bash completion for module or ml commands, the malicious module name, containing shell metacharacters, is evaluated as a command. This can lead to arbitrary command execution in the completing user's shell, impacting their confidentiality, integrity, and availability.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
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.2%
EPSS %ILE
11th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 15, 2026

Last Modified

September 21, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
🔬 Proof of concept available. Patch available. Sources: github, redhat.
github Patch Available🟡 PoC Available

Command injection in Bash completion via malicious module names containing shell meta-characters · Advisory · envmodules/modules · GitHub

https://github.com/envmodules/modules/security/advisories/GHSA-8hrw-p88g-qhmg
redhat

2465635 – (CVE-2026-85013) CVE-2026-85013 environment-modules: Command injection in environment-modules Bash completion via malicious module names containing shell metacharacters

https://bugzilla.redhat.com/show_bug.cgi?id=2465635
redhat Patch Available

CVE-2026-85013 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-85013

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatenvironment-modules-main-5.6.2-1.hum12026-09-07redhat

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
modules5.2.0-1 ... 5.7.0-1 (12 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
modules5.5.0-1 ... 5.7.0-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
modules5.5.0-1, 5.6.0-1, 5.6.1-1, 5.6.1-2
  • every version up to 5.6.1-3: fixed in 5.6.1-3
—

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 28× in last 7d / 71× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-05 04:15 UTCEG score recompute
  2. 2026-10-05 04:15 UTCVendor advisory
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 16:39 UTCVendor advisory
  5. 2026-10-04 05:03 UTCVendor advisory
  6. 2026-10-03 17:28 UTCEG score recompute
  7. 2026-10-03 17:28 UTCVendor advisory
  8. 2026-10-03 14:26 UTCEPSS rescore
  9. 2026-10-03 05:53 UTCVendor advisory
  10. 2026-10-02 18:18 UTCEG score recompute
  11. 2026-10-02 18:18 UTCVendor advisory
  12. 2026-10-02 17:57 UTCEPSS rescore
  13. 2026-10-02 06:41 UTCEG score recompute
  14. 2026-10-02 06:41 UTCVendor advisory
  15. 2026-10-01 19:50 UTCEPSS rescore
  16. 2026-10-01 19:03 UTCVendor advisory
  17. 2026-10-01 07:05 UTCVendor advisory
  18. 2026-09-30 19:30 UTCEG score recompute
  19. 2026-09-30 19:30 UTCVendor advisory
  20. 2026-09-30 15:04 UTCEPSS rescore
  21. 2026-09-30 07:55 UTCVendor advisory
  22. 2026-09-29 20:20 UTCEG score recompute
  23. 2026-09-29 20:20 UTCVendor advisory
  24. 2026-09-29 07:49 UTCEG score recompute
  25. 2026-09-29 07:49 UTCVendor advisory
Show 46 more
  1. 2026-09-28 20:14 UTCEG score recompute
  2. 2026-09-28 20:14 UTCVendor advisory
  3. 2026-09-28 13:52 UTCEPSS rescore
  4. 2026-09-28 08:38 UTCVendor advisory
  5. 2026-09-27 21:03 UTCEG score recompute
  6. 2026-09-27 21:03 UTCVendor advisory
  7. 2026-09-27 13:48 UTCEPSS rescore
  8. 2026-09-27 09:28 UTCVendor advisory
  9. 2026-09-26 21:52 UTCEG score recompute
  10. 2026-09-26 21:52 UTCVendor advisory
  11. 2026-09-26 15:59 UTCEPSS rescore
  12. 2026-09-26 10:17 UTCEG score recompute
  13. 2026-09-26 10:17 UTCVendor advisory
  14. 2026-09-25 22:39 UTCVendor advisory
  15. 2026-09-25 09:58 UTCVendor advisory
  16. 2026-09-24 22:23 UTCEG score recompute
  17. 2026-09-24 22:23 UTCVendor advisory
  18. 2026-09-24 14:04 UTCEPSS rescore
  19. 2026-09-24 10:47 UTCVendor advisory
  20. 2026-09-23 23:11 UTCEG score recompute
  21. 2026-09-23 23:11 UTCVendor advisory
  22. 2026-09-23 17:54 UTCEPSS rescore
  23. 2026-09-23 11:09 UTCVendor advisory
  24. 2026-09-22 23:34 UTCEG score recompute
  25. 2026-09-22 23:34 UTCVendor advisory
  26. 2026-09-22 16:01 UTCEPSS rescore
  27. 2026-09-22 11:41 UTCVendor advisory
  28. 2026-09-22 00:06 UTCEG score recompute
  29. 2026-09-22 00:06 UTCVendor advisory
  30. 2026-09-21 21:09 UTCEPSS rescore
  31. 2026-09-21 12:30 UTCEG score recompute
  32. 2026-09-21 12:30 UTCVendor advisory
  33. 2026-09-21 11:50 UTCEG score recompute
  34. 2026-09-21 04:37 UTCEG score recompute
  35. 2026-09-20 20:16 UTCEPSS rescore
  36. 2026-09-19 17:48 UTCEG score recompute
  37. 2026-09-19 06:12 UTCEG score recompute
  38. 2026-09-18 19:28 UTCEPSS rescore
  39. 2026-09-18 06:58 UTCEG score recompute
  40. 2026-09-17 19:32 UTCEPSS rescore
  41. 2026-09-16 17:55 UTCEG score recompute
  42. 2026-09-16 14:09 UTCEPSS rescore
  43. 2026-09-15 18:33 UTCEG score recompute
  44. 2026-09-15 17:28 UTCEG score recompute
  45. 2026-09-15 15:24 UTCEG score recompute
  46. 2026-09-15 15:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-85013?
CVE-2026-85013 is a high vulnerability published on September 15, 2026. A flaw was found in environment-modules. A local attacker can exploit this vulnerability by placing a maliciously named modulefile in a location visible to the victim's MODULEPATH. When the victim uses Bash completion for module or ml commands, the malicious module name, containing shell…
When was CVE-2026-85013 disclosed?
CVE-2026-85013 was first published on September 15, 2026, with the most recent update on September 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-85013 actively exploited?
CVE-2026-85013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-85013?
CVE-2026-85013 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-85013?
A fix for CVE-2026-85013 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-85013?

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

Book a Demo →Browse All CVEs