# CVE-2026-119578: MONAI 1.6.0 before 1.6.1 Code Execution via Auto3DSeg algo_from_json()


- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-2wx3-8x3w-r8qv, GHSA-rx25-w8hq-hr3g

## What is CVE-2026-119578?

CVE-2026-119578 is a high-severity vulnerability in Project-MONAI MONAI, published on 30 Oct 2026. 

### Official 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.

Weakness: CWE-470 (Use of Externally-Controlled Input to Select Classes or Code)

## Which versions are affected by CVE-2026-119578?


## How do I fix CVE-2026-119578?

No fix has been published for CVE-2026-119578 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119578 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119578 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119578 and fix it if it is affected.

What it is: CVE-2026-119578 is a high-severity vulnerability in Project-MONAI MONAI, published on 30 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119578 exists.

Affected product: Project-MONAI MONAI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119578/ (Markdown: https://insights.sbomify.com/CVE-2026-119578/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119578
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119578
- OSV: https://osv.dev/vulnerability/CVE-2026-119578

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119578/
Summaries are generated and may contain mistakes; the official description above is the record.