Quick answers
- Is CVE-2026-118683 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-118683 being exploited in the wild.
- How severe is CVE-2026-118683?
- High severity, with a CVSS score of 8.8, published 28 October 2026.
- Which products and versions are affected?
- Project-MONAI MONAI 1.2.0 to 1.6.0.
- Is there a fix for CVE-2026-118683?
- Yes: fixed in 1.6.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-118683 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-118683?
- Check whether you run Project-MONAI MONAI at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.6.1
Technical details
ConfigWorkflow.__init__ passes a bundle's configs/logging.conf to logging.config.fileConfig() without validation, which eval()s the handler class and args fields in the INI file. An attacker can craft a malicious logging.conf with arbitrary Python code in the handler class field that executes at workflow construction time (before initialize or run), triggered by monai.bundle.load(), monai.bundle.run(), or direct ConfigWorkflow instantiation. This is a supply-chain attack vector affecting users who load bundles from public repositories like Hugging Face or NGC.
Affected products
- Project-MONAI MONAI 1.2.0 to 1.6.0
Timeline
- 2026-10-13: disclosed
- 2026-10-28: advisory