CVE-2026-100841

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In MONAI 1.6.0, PersistentDataset (monai/data/dataset.py) explicitly rejects the combination track_meta=True with weights_only=True, forcing users who cache MetaTensors (the default tensor type in MONAI >= 1.0) to run torch.load(hashfile, weights_only=False). Related cache helpers in monai/data/utils.py also call pickle.loads on cached content and derive cache keys with hashlib.md5. As a result, a local user with write access to a shared or world-writable cache_dir (e.g. /tmp/monai_cache, HPC scratch, ~/.cache/monai) can place a malicious pickle file that is deserialized the next time another user's MONAI pipeline reads the cache, resulting in arbitrary code execution in that user's context. All released versions of the monai pip package are affected; no patched version is available as of the advisory.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
35
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (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 27, 2026

Last Modified

September 30, 2026

Advisory Details (2)

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

MONAI 1.6.0 PersistentDataset Remote Code Execution via Pickle Cache | Advisories | VulnCheck

https://www.vulncheck.com/advisories/monai-1.6.0-persistentdataset-remote-code-execution-via-pickle-cache
github Patch Available

PersistentDataset forces weights_only=False with MetaTensor + data/utils.py uses pickle.loads/md5 — local-user pickle RCE via shared cache_dir · Advisory · Project-MONAI/MONAI · GitHub

https://github.com/Project-MONAI/MONAI/security/advisories/GHSA-636w-j999-g7x5

Vendor Advisories for CVE-2026-100841(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 rangeFixed inDependents
monai———

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 34× in last 7d / 39× 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-04 09:21 UTCGHSA enrichment
  2. 2026-10-03 22:32 UTCEG score recompute
  3. 2026-10-03 22:32 UTCGHSA enrichment
  4. 2026-10-03 14:25 UTCEPSS rescore
  5. 2026-10-03 11:41 UTCGHSA enrichment
  6. 2026-10-03 00:33 UTCEG score recompute
  7. 2026-10-03 00:33 UTCGHSA enrichment
  8. 2026-10-02 13:44 UTCGHSA enrichment
  9. 2026-10-02 02:46 UTCEG score recompute
  10. 2026-10-02 02:45 UTCGHSA enrichment
  11. 2026-10-01 19:49 UTCEPSS rescore
  12. 2026-10-01 15:46 UTCGHSA enrichment
  13. 2026-10-01 04:57 UTCGHSA enrichment
  14. 2026-09-30 18:07 UTCGHSA enrichment
  15. 2026-09-30 16:35 UTCEG score recompute
  16. 2026-09-30 16:35 UTCGHSA enrichment
  17. 2026-09-30 15:02 UTCEPSS rescore
  18. 2026-09-30 05:45 UTCGHSA enrichment
  19. 2026-09-29 18:52 UTCEG score recompute
  20. 2026-09-29 18:52 UTCGHSA enrichment
  21. 2026-09-29 15:20 UTCEPSS rescore
  22. 2026-09-29 08:02 UTCEG score recompute
  23. 2026-09-29 08:02 UTCGHSA enrichment
  24. 2026-09-28 21:13 UTCGHSA enrichment
  25. 2026-09-28 14:26 UTCEG score recompute
Show 14 more
  1. 2026-09-28 14:26 UTCGHSA enrichment
  2. 2026-09-28 14:02 UTCEG score recompute
  3. 2026-09-28 14:02 UTCGHSA enrichment
  4. 2026-09-28 13:50 UTCEPSS rescore
  5. 2026-09-28 04:12 UTCGHSA enrichment
  6. 2026-09-27 17:24 UTCEG score recompute
  7. 2026-09-27 17:24 UTCGHSA enrichment
  8. 2026-09-27 16:35 UTCEG score recompute
  9. 2026-09-27 16:35 UTCGHSA enrichment
  10. 2026-09-27 13:27 UTCEG score recompute
  11. 2026-09-27 13:27 UTCGHSA enrichment
  12. 2026-09-27 02:37 UTCEG score recompute
  13. 2026-09-27 01:53 UTCEG score recompute
  14. 2026-09-27 01:49 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-100841?
CVE-2026-100841 is a high vulnerability published on September 27, 2026. In MONAI 1.6.0, PersistentDataset (monai/data/dataset.py) explicitly rejects the combination trackmeta=True with weightsonly=True, forcing users who cache MetaTensors (the default tensor type in MONAI >= 1.0) to run torch.load(hashfile, weightsonly=False). Related cache helpers in…
When was CVE-2026-100841 disclosed?
CVE-2026-100841 was first published on September 27, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100841 actively exploited?
CVE-2026-100841 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100841?
CVE-2026-100841 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-100841?
A fix for CVE-2026-100841 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100841 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-100841

Explore →

Is Your Infrastructure Affected by CVE-2026-100841?

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

Book a Demo →Browse All CVEs