Live › vulnerability › CVE-2026-118683
Go to dashboardMONAI versions 1.2.0 through 1.6.0 pass a bundle's configs/logging.conf to Python's logging.config.fileConfig, which evaluates handler class and argument fields as code. An attacker who publishes a malicious bundle gets arbitrary Python execution on the machine of anyone who loads or runs it.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 19:34 UTC. All times on this page are UTC.
Teams that load MONAI bundles, especially ones downloaded from public model hubs or shared by outside parties, since the bundle's logging.conf is executed when ConfigWorkflow is constructed. Systems that only use bundles they authored or vetted, or that run no MONAI bundle workflows, are less exposed.
No product ranges from the sources yet.
python -c "import monai; print(monai.__version__)"; versions below 1.6.1 are in range.configs/logging.conf for unexpected eval-style handler or args values.1.6.1 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
MONAI from 1.2.0 before 1.6.1 contains a remote code execution vulnerability in ConfigWorkflow.init, which passes a bundle's configs/logging.conf to logging.config.fileConfig that eval()s handler class and args fields. Attackers can publish a malicious bundle whose logging.conf runs arbitrary Python at workflow construction when a victim loads or runs the bundle.
This page as .md · .json · in your agent: get_signal("CVE-2026-118683")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.