MONAI 1.6.0 before 1.6.1 Code Execution via Auto3DSeg algo_from_json()
MONAI 1.6.0 before 1.6.1 is affected when a crafted Auto3DSeg work directory is loaded with AutoRunner or import_bundle_algo_history. The vendor gives no separate severity rating. Fixed in 1.6.1.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.6.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
MONAI, an open-source Python framework for medical imaging AI, is affected through its Auto3DSeg component. Attackers who supply a crafted work directory can get arbitrary code to run on a victim's system when the victim uses that directory with the affected functions, potentially giving them full control over the machine.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
MONAI from 1.6.0 before 1.6.1 contains a remote code execution vulnerability in Auto3DSeg algo_from_json() that allows attackers to run Python code via a crafted work directory's algo_object.json. Attackers can ship a malicious algorithm_templates module plus a target name that is imported and instantiated when victims call AutoRunner or import_bundle_algo_history, executing code under default configuration.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Project-MONAI MONAI
From 1.6.0 · fixed in 1.6.1
References 2
GitHub · Project-MONAI/MONAI
Questions about CVE-2026-119578
What does this mean?
Loading a crafted Auto3DSeg work directory with AutoRunner or import_bundle_algo_history can run arbitrary code as the user running the Auto3DSeg workload.Source: github.com
Am I affected, and how do I check?
The product range is MONAI 1.6.0 up to but not including 1.6.1, but the GitHub advisory lists affected versions as 1.6.0rc1 and earlier, so the sources do not match exactly. The affected setup involves loading an Auto3DSeg work directory with AutoRunner or import_bundle_algo_history; check your installed version with python -c "import monai; print(monai.__version__)".Source: github.com
What should I do about it?
Upgrade MONAI to 1.6.1 or later, which is the listed fixed version.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data