rootpwn

high · CVSS v3 7 · CVSS v4 7.3 · EPSS 0.00148

CVE-2026-100842

MONAI versions up to 1.6.0 contain an eval injection flaw in _get_fake_spatial_shape() that allows attackers to execute arbitrary code via c

Overview

MONAI versions up to 1.6.0 contain an eval injection flaw in _get_fake_spatial_shape() that allows attackers to execute arbitrary code via crafted bundle metadata. The vulnerability bypasses the intended name whitelist by using AST nodes that contain no ast.Name, enabling object introspection chains. It can be exploited in the non‑default verify_net_in_out CLI flow.

Description

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.

Impact

The flaw compromises confidentiality, integrity, and availability of systems running vulnerable MONAI bundles. Attackers can gain full code execution, potentially exfiltrating data, modifying models, or disrupting services. Defenders should treat affected deployments as compromised until patched.

Remediation

Upgrade MONAI to version 1.6.1 or later where the eval guard is tightened. If upgrade is not possible, remove or sanitize bundle metadata that feeds _get_fake_spatial_shape(), or disable the verify_net_in_out CLI flow. Monitor for anomalous process creation or unexpected eval usage.

Risk context

Severity is high with CVSS v3 7.0 and v4 7.3, but EPSS is low at 0.00148, indicating a rare exploitation likelihood. Nonetheless, the potential impact warrants prompt patching.

Affected products

  • MONAI 1.6.0
  • MONAI 1.5.x

Scores

Severity
high
CVSS v2
6
CVSS v3
7
CVSS v4
7.3
EPSS
0.00148

eval-injection Python AST code-execution MONAI high-severity EPSS-low

← All CVEs

Related CVEs

high

CVE-2026-100744

A flaw has been found in coollabsio Coolify up to 4.1.2. The affected element is an unknown function of the file app/Http/Middleware/CanUpdateResource.php of the component Route-Level Middleware. Executing a manipulation can lead to missing authorization. The attack may be launched remotely. The exploit has been published and may be used. Upgrading to version 4.2.0 is sufficient to fix this issue. This patch is called 39ae16de4248075de8c08f3259114e064b20d52d. It is advisable to upgrade the affected component.

View analysis

high

CVE-2025-71423

Edgelesssys Contrast is a confidential-computing runtime for Kubernetes. In versions 1.9.0 before 1.12.2, the initializer logs the full NewMeshCert response — which contains the workload secret — to standard output at INFO level. As a result, workload secrets are exposed to any Kubernetes user with get or list permission on pods/logs. Because workload secrets are used for encrypted storage and Vault integration, those must also be considered compromised. This is a regression of GHSA-h5f8-crrq-4pw8.

View analysis

high

CVE-2025-71425

Contrast (Edgeless Systems) before 1.8.1 logs the workload secret to stderr, and thus to Kubernetes logs, when the Contrast initializer is configured with CONTRAST_LOG_LEVEL set to info or debug. Because info is the default, all installations that do not customize the initializer log level are affected. This exposes workload secrets — normally accessible only to the Contrast Coordinator, the initializer, the seedshare owner, and the workload owner — to Kubernetes users with get or list permission on pods/logs and to anyone with read access to the Kubernetes log storage, such as the cloud provider. Deployments that do not use workload secrets are unaffected.

View analysis

high

CVE-2025-71426

Contrast is a confidential-computing runtime for Kubernetes. In versions before 1.4.1, a recovering Coordinator does not verify the seed supplied by the recovering party. An attacker can therefore stand up a rogue Coordinator whose manifest passes validation but whose secret seed is attacker-controlled. If network traffic is redirected from the legitimate Coordinator to the attacker's Coordinator, a workload owner can be impersonated when they either set a new manifest without comparing the returned root CA certificate against the existing one (the default behavior of the contrast CLI) or verify the Coordinator without comparing the root CA certificate against a trusted reference. Under these conditions the attacker can issue certificates that chain back to the rogue Coordinator's root CA and recover arbitrary workload secrets of workloads deployed after the attack. Secrets of the legitimate Coordinator (seed, workload secrets, CA), workload integrity, and certificates chaining to the mesh CA are not affected.

View analysis