CVE-2026-118683: MONAI · Code Injection
Affects MONAISource CVE Database V5
Not known to be exploited · CVSS 8.6 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:N/PR:N/UI:A/VC:H/VI:H/VA:H/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. No other mitigations are specified. Applying the official patch eliminates the risk of this remote code execution vulnerability.
Description
MONAI versions from 1.2.0 up to but not including 1.6.1 contain a remote code execution vulnerability in the ConfigWorkflow.__init__ method. This flaw arises because the logging configuration file (logging.conf) is processed using logging.config.fileConfig, which internally uses eval() on handler class and args fields. An attacker can craft a malicious bundle with a specially designed logging.conf that executes arbitrary Python code when the bundle is loaded or run, leading to remote code execution.