CVE-2026-100842

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.0 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-09-27) is not newer than that change (2026-09-30), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-87846 (ENISA EUVD) · GHSA-j335-cfj5-2fw8 (GitHub Security Advisories) · PYSEC-2026-4017 (OSV.dev)Source: ENISA EUVD

8.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.2%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

MONAI through 1.6.0 contains an eval injection vulnerability in _get_fake_spatial_shape() in monai/bundle/scripts.py. The function validates shape expressions with a helper that walks the AST and only collects ast.Name nodes, rejecting any name other than 'p' or 'n', before passing the string to eval(). Expressions built solely from constants and attribute, subscript, or call nodes (for example "(1).__class__.__bases__[0].__subclasses__()" or "int.__class__.__init__.__globals__") contain no ast.Name nodes and therefore bypass the allowlist. Because the shape value originates from bundle metadata consumed by _get_real_input_data and verify_net_in_out (reachable through the bundle 'verify_net_in_out' CLI flow), an attacker who can influence a bundle's metadata can escape the eval sandbox via object introspection chains and achieve code execution in this non-default flow.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.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.2%
EPSS %ILE
8th
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 (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). 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

September 27, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 27, 2026
Patch available. Sources: github.
Web page

MONAI through 1.6.0 _get_fake_spatial_shape eval() Sandbox Bypass via Attribute Chains | Advisories | VulnCheck

https://www.vulncheck.com/advisories/monai-through-1.6.0-get-fake-spatial-shape-eval-sandbox-bypass-via-attribute-chains
GitHub advisoryMentions a patch (unverified)

_get_fake_spatial_shape() ast.Name-only allowlist bypassable via Attribute chains — eval sandbox escape · Advisory · Project-MONAI/MONAI · GitHub

https://github.com/Project-MONAI/MONAI/security/advisories/GHSA-h89g-r5pc-wxfm

Vendor Advisories for CVE-2026-100842(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
monai0.0.1 ... 1.6.0 (44 versions)
  • every version up to 1.6.1rc0: fixed in 1.6.1rc0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 113 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 13 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  6. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-11-08 05:39 UTCEchelonGraph re-scored
  8. 2026-11-08 05:39 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  9. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  12. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  13. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-11-01 02:28 UTCEchelonGraph re-scored
  17. 2026-11-01 02:28 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  18. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-10-25 15:57 UTCEchelonGraph re-scored
Show 75 more
  1. 2026-10-24 23:16 UTCEchelonGraph re-scored
  2. 2026-10-24 23:16 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  3. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  4. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  5. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-10-18 05:11 UTCEchelonGraph re-scored
  11. 2026-10-17 20:05 UTCEchelonGraph re-scored
  12. 2026-10-17 20:05 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  13. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  14. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  15. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  16. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  17. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  18. 2026-10-12 16:41 UTCEchelonGraph re-scored
  19. 2026-10-12 02:48 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  20. 2026-10-11 20:16 UTCEchelonGraph re-scored
  21. 2026-10-11 18:28 UTCEchelonGraph re-scored
  22. 2026-10-11 13:51 UTCEchelonGraph re-scored
  23. 2026-10-11 13:50 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  24. 2026-10-11 00:18 UTCEchelonGraph re-scored
  25. 2026-10-11 00:17 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  26. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  27. 2026-10-10 11:13 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  28. 2026-10-09 22:17 UTCEchelonGraph re-scored
  29. 2026-10-09 22:16 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  30. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  31. 2026-10-09 09:19 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  32. 2026-10-08 20:23 UTCEchelonGraph re-scored
  33. 2026-10-08 20:23 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  34. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  35. 2026-10-08 07:22 UTCEchelonGraph re-scored
  36. 2026-10-08 07:22 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  37. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  38. 2026-10-07 18:26 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  39. 2026-10-07 05:30 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  40. 2026-10-06 16:33 UTCEchelonGraph re-scored
  41. 2026-10-06 16:33 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  42. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  43. 2026-10-06 03:35 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  44. 2026-10-06 03:34 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  45. 2026-10-06 03:34 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  46. 2026-10-06 03:33 UTCEchelonGraph re-scored
  47. 2026-10-06 03:33 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  48. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-10-05 14:35 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  50. 2026-10-05 01:39 UTCEchelonGraph re-scored
  51. 2026-10-05 01:39 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  52. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  53. 2026-10-04 12:43 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  54. 2026-10-03 23:47 UTCEchelonGraph re-scored
  55. 2026-10-03 23:47 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  56. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  57. 2026-10-03 10:49 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  58. 2026-10-02 21:53 UTCEchelonGraph re-scored
  59. 2026-10-02 21:53 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  60. 2026-10-02 08:56 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  61. 2026-10-01 19:59 UTCEchelonGraph re-scored
  62. 2026-10-01 19:59 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  63. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  64. 2026-10-01 07:03 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  65. 2026-09-30 18:07 UTCEchelonGraph re-scored▲ 1.80
  66. 2026-09-30 18:07 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  67. 2026-09-30 18:04 UTCNVD updateCVSS v3 → 8.8
  68. 2026-09-30 17:27 UTCEchelonGraph re-scored
  69. 2026-09-30 17:27 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  70. 2026-09-30 17:01 UTCEchelonGraph re-scored
  71. 2026-09-30 17:01 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  72. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  73. 2026-09-30 12:43 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0
  74. 2026-09-29 23:47 UTCEchelonGraph re-scored
  75. 2026-09-29 23:47 UTCGHSA enrichmentGHSA-j335-cfj5-2fw8 · GitHub severity HIGH · GitHub CVSS 7.0

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-100842?
CVE-2026-100842 is a high-severity vulnerability; its CVE record was published on September 27, 2026. MONAI through 1.6.0 contains an eval injection vulnerability in _get_fake_spatial_shape() in monai/bundle/scripts.py. The function validates shape expressions with a helper that walks the AST and only collects ast.Name nodes, rejecting any name other than 'p' or 'n', before passing the string to…
When was CVE-2026-100842 made public?
CVE-2026-100842 was made public on August 18, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 27, 2026. 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-100842 actively exploited?
CVE-2026-100842 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100842?
CVE-2026-100842 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-100842?
A fix for CVE-2026-100842 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100842 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-100842

Explore →

Is Your Infrastructure Affected by CVE-2026-100842?

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

Book a Demo →Browse All CVEs