CVE-2026-100840: MONAI: code execution via malicious bundle config

HIGHPoC AVAILABLECISA: ATTEND
Published September 27, 2026
CISO Take

MONAI through 1.6.0 resolves `_target_` values in bundle configurations to any importable callable and passes `$` expressions to Python `eval()`. A malicious bundle therefore runs arbitrary code as soon as someone loads it with `monai.bundle.load()` or `monai.bundle.run()`. The CVSS is 7.8 (local, user interaction required), the EPSS is low at 0.00215 (89th percentile), it is not in CISA KEV, and there is no public exploit or Nuclei template. CISA SSVC rates it ATTEND, so it deserves scheduled attention rather than an emergency response. The real risk is supply chain: medical imaging teams often pull pretrained bundles from the MONAI Model Zoo, Hugging Face or colleagues, and those workstations and GPU servers often hold sensitive data. Until a fixed release is available, only load bundles from sources you trust and have reviewed, and run bundle loading in isolated, least-privilege environments. Follow GHSA-873f-pvrv-4x83 for the patch.

Sources:NVDEPSSGitHub Advisoryvulncheck.comATLASCISA SSVC

What is the risk?

Overall risk is MEDIUM-HIGH for organizations that load third-party MONAI bundles, and LOW for those that use only internally built bundles. The code is trivial to exploit once a victim loads a crafted bundle: attack complexity is low and no privileges are needed. Exploitation does require user interaction (loading the bundle) and local access, which limits mass exploitation. Impact on confidentiality, integrity and availability is high, because the code runs with the privileges of the user or service loading the bundle. EPSS is low (0.00215), there is no KEV listing and no public exploit, so active exploitation is not currently observed. Exposure is higher in healthcare and research settings, where unvetted models are routinely shared.

How does the attack unfold?

Malicious Bundle Publication
Attacker publishes a bundle with a crafted config containing a malicious `_target_` or `$` expression to a public hub or shared location.
AML.T0058
User Execution
Victim downloads the bundle and loads it via monai.bundle.load() or monai.bundle.run().
AML.T0011.000
Code Execution
The configuration engine resolves arbitrary callables and evaluates expressions with eval(), running attacker code with the user's privileges.
AML.T0050
Impact
Attacker steals data, credentials and model artifacts and may establish a foothold for lateral movement from the compromised ML host.
AML.T0025

What systems are affected?

PackageEcosystemVulnerable RangePatched
MONAIpip—No patch
8.8KOpenSSF 7.8129 dependentsPushed 4d ago41% patched~22d to patchFull package profile →

Do you use MONAI? You're affected.

How severe is it?

CVSS 3.1
7.8 / 10
EPSS
0.3%
chance of exploitation in 30 days
Higher than 25% of all CVEs
Exploitation Status
Exploit Available
Exploitation: MEDIUM
Sophistication
Trivial
Exploitation Confidence
medium
○CISA SSVC: Public PoC
○Public PoC indexed (trickest/cve)
Composite signal derived from CISA KEV, VulnCheck KEV, CISA SSVC, EPSS, Metasploit, Exploit-DB, trickest/cve, Nuclei templates, and inthewild.io exploitation reports.

What is the attack surface?

AVACPRUISCIA
AVLocal
ACLow
PRNone
UIRequired
SUnchanged
CHigh
IHigh
AHigh

What should I do?

1 step
  1. 1) Monitor the GitHub advisory GHSA-873f-pvrv-4x83 and the VulnCheck advisory, and upgrade MONAI as soon as a release newer than 1.6.0 with a fix is available. 2) Until then, load only bundles from trusted, verified sources; inspect the config files (JSON/YAML) for _target_ entries that reference unexpected modules and for $ expressions before loading. 3) Run monai.bundle.load() and monai.bundle.run() in sandboxed containers or VMs with no credentials, restricted network egress and read-only data mounts. 4) Do not run bundle loading as root or with access to production secrets or PHI. 5) Pin bundle sources and verify hashes or signatures in CI/CD and MLOps pipelines. 6) Detection: alert on unexpected child processes, outbound connections or file writes from Python processes running MONAI, and audit which bundles were loaded from external sources.

What does CISA's SSVC say?

DecisionAttend
Exploitationpoc
AutomatableNo
Technical Impacttotal

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act
Art. 15-Accuracy, robustness and cybersecurity
ISO 42001
A.10.3-Suppliers
NIST AI RMF
GOVERN 6.1-Policies and procedures for third-party AI risk
OWASP LLM Top 10
LLM03-Supply Chain

Frequently Asked Questions

What is CVE-2026-100840?

MONAI through 1.6.0 resolves `_target_` values in bundle configurations to any importable callable and passes `$` expressions to Python `eval()`. A malicious bundle therefore runs arbitrary code as soon as someone loads it with `monai.bundle.load()` or `monai.bundle.run()`. The CVSS is 7.8 (local, user interaction required), the EPSS is low at 0.00215 (89th percentile), it is not in CISA KEV, and there is no public exploit or Nuclei template. CISA SSVC rates it ATTEND, so it deserves scheduled attention rather than an emergency response. The real risk is supply chain: medical imaging teams often pull pretrained bundles from the MONAI Model Zoo, Hugging Face or colleagues, and those workstations and GPU servers often hold sensitive data. Until a fixed release is available, only load bundles from sources you trust and have reviewed, and run bundle loading in isolated, least-privilege environments. Follow GHSA-873f-pvrv-4x83 for the patch.

Is CVE-2026-100840 actively exploited?

Proof-of-concept exploit code is publicly available for CVE-2026-100840, increasing the risk of exploitation.

How to fix CVE-2026-100840?

1) Monitor the GitHub advisory GHSA-873f-pvrv-4x83 and the VulnCheck advisory, and upgrade MONAI as soon as a release newer than 1.6.0 with a fix is available. 2) Until then, load only bundles from trusted, verified sources; inspect the config files (JSON/YAML) for `_target_` entries that reference unexpected modules and for `$` expressions before loading. 3) Run `monai.bundle.load()` and `monai.bundle.run()` in sandboxed containers or VMs with no credentials, restricted network egress and read-only data mounts. 4) Do not run bundle loading as root or with access to production secrets or PHI. 5) Pin bundle sources and verify hashes or signatures in CI/CD and MLOps pipelines. 6) Detection: alert on unexpected child processes, outbound connections or file writes from Python processes running MONAI, and audit which bundles were loaded from external sources.

What systems are affected by CVE-2026-100840?

This vulnerability affects the following AI/ML architecture patterns: training pipelines, model serving, medical imaging workflows, MLOps pipelines, Jupyter notebooks.

What is the CVSS score for CVE-2026-100840?

CVE-2026-100840 has a CVSS v3.1 base score of 7.8 (HIGH). The EPSS exploitation probability is 0.31%.

What is the AI security impact?

Affected AI Architectures

training pipelinesmodel servingmedical imaging workflowsMLOps pipelinesJupyter notebooks

MITRE ATLAS Techniques

AML.T0010.003Model
AML.T0011.000Unsafe AI Artifacts
AML.T0050Command and Scripting Interpreter
AML.T0058Publish Poisoned Models
AML.T0112.001AI Artifacts

Compliance Controls Affected

EU AI Act: Art. 15
ISO 42001: A.10.3
NIST AI RMF: GOVERN 6.1
OWASP LLM Top 10: LLM03

What are the technical details?

Original Advisory

MONAI through 1.6.0 contains a remote code execution vulnerability in the bundle configuration engine that resolves _target_ values to arbitrary importable callables without an allow list and passes $ expressions to Python eval(). Attackers can publish a malicious bundle with crafted configuration containing arbitrary code that executes when a victim loads the bundle using monai.bundle.load() or monai.bundle.run().

Exploitation Scenario

An attacker publishes a plausible-looking MONAI bundle (for example a segmentation model for a popular imaging task) to a public repository, model hub or shared drive. The `configs/*.json` file contains a `_target_` pointing to a callable such as `os.system` or `subprocess.run`, or a `$` expression that calls `__import__('os').system(...)`. A researcher or ML engineer downloads the bundle and runs `monai.bundle.load()` or `monai.bundle.run()` to test it. The payload executes with that user's privileges, steals cloud credentials, SSH keys and access to imaging datasets, and installs a reverse shell on the GPU workstation. The attacker then moves laterally into the research or hospital network.

Weaknesses (CWE)

CWE-95 — Improper Neutralization of Directives in Dynamically Evaluated Code: The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. "eval").

  • [Architecture and Design, Implementation] If possible, refactor your code so that it does not need to use eval() at all.
  • [Implementation] Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylis

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Timeline

Published
September 27, 2026
Last Modified
September 30, 2026
First Seen
September 27, 2026

Related Vulnerabilities