CVE-2026-118684: MONAI · Weak Cryptography
Affects MONAISource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 1.6.1 soon.
Data as of 28 Oct 2026, 19:27 UTC
- Patch
- Available – fixed in 1.6.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade MONAI to 1.6.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Project-MONAIMONAI | Affected
| Fixed in
|
PyPIMONAIpkg:pypi/MONAIOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade MONAI to version 1.6.1 or later, where this vulnerability is fixed. The fix addresses the insufficient integrity verification and removes reliance on the insecure MD5 hash as default. No other mitigation steps are indicated.
Description
MONAI versions before 1.6.1 have a vulnerability in the check_hash() function where the integrity verification is insufficient. Specifically, if the hash value is None, the function incorrectly returns True, and MD5 is used as the default hash algorithm. This flaw allows attackers who can perform man-in-the-middle or registry compromise attacks to substitute malicious bundles, datasets, or model archives downloaded without hashes, potentially leading to malicious file delivery and code execution.