MONAI: MONAILabel Server Crash and Silent Inference Corruption via Crafted DICOM (pydicom DS/IS Validation Bypass)

published 2026-10-27 12 d ago modified 2026-11-05 3 d ago also GHSA-6hp3-vr39-rqw8 , EUVD-2026-117795

cvss: 9.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits: 0; none known

MONAI (Medical Open Network for AI) is an AI toolkit for health care imaging. Prior to 1.6.1, PydicomReader._get_affine() trusts non-finite values in the DICOM PixelSpacing, ImagePositionPatient, and ImageOrientationPatient fields and composes them into an affine matrix without validation. An unauthenticated attacker who can upload a crafted DICOM to a default MONAILabel deployment can propagate NaN or infinity values through LoadImaged, Spacingd, model inference, and output writing, causing inference failures, persistent datastore poisoning, or geometrically corrupted results. This issue is fixed in version 1.6.1.

Patch / fix

fixed in 1 links 3

pypi monai 1.6.1

github.com/Project-MONAI/MONAI@434c094 commit
github.com/Project-MONAI/MONAI#9087 pull request
github.com/Project-MONAI/MONAI/releases/tag/1.6.1 release

CISA SSVC

Exploitation: Proof of concept is public
Automatable: yes
Technical impact: partial
Assessed: 3 d ago (2026-11-05)

Exploit prediction

0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/Project-MONAI/MONAI/security/advisories/GHSA-6hp3-vr39-rqw8 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:L
GitHub	3.1	9.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:L

Affected packages

ecosystem	package	affected	fixed in
pypi	monai	<1.6.1	1.6.1

Affected products

Project-MONAI MONAI

Classification

Weakness

CWE-20 Improper Input Validation
CWE-682 Incorrect Calculation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary