# CVE-2026-109361: MONAI 1.2.0 before 1.6.1 Insecure Deserialization RCE via nnUNetV2Runner postprocessing_file Path

> Attackers can execute arbitrary code by modifying inference configuration to point to a malicious pickle file in MONAI.

- **Severity:** High 7.0 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-7hmf-j253-4p2j, GHSA-8f32-8649-rv87

## What is CVE-2026-109361?

CVE-2026-109361 is a high-severity unsafe deserialization vulnerability in Project-MONAI MONAI, published on 12 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

MONAI 1.2.0 before 1.6.1 contains an insecure deserialization vulnerability in nnUNetV2Runner that unpickles the postprocessing_file path read from inference_information.json without confining it to the results directory. Attackers who can modify inference_information.json can point it at a malicious pickle elsewhere on the filesystem to execute code when predict_ensemble_postprocessing runs.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-109361 being exploited?

There is no known exploitation of CVE-2026-109361 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109361 is a high-severity unsafe deserialization vulnerability in Project-MONAI MONAI, published on 12 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-109361 in the wild and no public exploit code.

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-109361/ (Markdown: https://insights.sbomify.com/CVE-2026-109361/index.md)
```

## Sources

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

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