Project-MONIA MONAI Label remote code execution via path traversal in datastore API
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Default setups
Summary
MONAI Label contains a directory traversal flaw in the image parameter of its PUT /datastore/image endpoint, which can lead to remote code execution. An attacker can reach it remotely over the network without logging in and without any user action.
Written by a model
Original description
monailabel (aka MONAI Label) through 0.8.5 allows directory traversal, with resultant remote code execution, via the image parameter to the PUT /datastore/image endpoint, as exploited in the wild starting in September 2026.
What to do
Check every install: default setups are affected.
Workaround: No fix is recorded in the checked facts. Limit access to the PUT /datastore/image endpoint to trusted callers, and if authentication is enabled, restrict the ANNOTATOR role to people who need it.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133968 (monailabel (aka MONAI Label) through 0.8.5 allows directory traversal, with resultant remote code execution, via the image parameter to…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133968 (entry last updated 2026-11-20):
Affected:
- PyPI package monailabel: through 0.8.5
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The server's PUT /datastore/image endpoint is reachable by the attacker. (source: https://github.com/Project-MONAI/MONAILabel/security/advisories/GHSA-qc22-rmgc-vg94)
- If authentication is enabled, the attacker needs the ANNOTATOR role. (source: https://github.com/Project-MONAI/MONAILabel/security/advisories/GHSA-qc22-rmgc-vg94)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-133968 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133968 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.theregister.com/security/2026/11/20/china-attackers-deployed-ai-agents-that-autonomously-found-and-exploited-a-0-day-to-take-over-a-university-server/5311382
- https://github.com/Project-MONAI/MONAILabel/security/advisories/GHSA-qc22-rmgc-vg94
- https://github.com/Project-MONAI/MONAILabel/pull/1915
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133968
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133968"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure22/25Default setups, reachable over the network without a login
- Reach10/20Affects PyPI packages
- Severity9.8/10CVSS 9.8
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 87 if added to CISA KEV
- Would score about 82 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · Project-MONAI/MONAILabel · Advisory GHSA-qc22-rmgc-vg94 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133968 |
| Record | NVD · CVE-2026-133968 |
| Write-ups 1Establishes: Technical detail and context. | |
| Link | theregister.com · security/2026/11/20/china-attackers-deployed-ai-agents-that-autonomously-found-and-exploited-a-0-day-to-take-over-a-university-server/5311382 |
| Other links 1 | |
| Repository | GitHub · Project-MONAI/MONAILabel · Pull request #1915 |
Questions about CVE-2026-133968
Is CVE-2026-133968 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. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The PUT /datastore/image endpoint accepts a caller-controlled image parameter that allows directory traversal. This lets an attacker write arbitrary files on the server, which can lead to remote code execution or denial of service by overwriting configuration files.
Source: github.com
Which versions are affected by CVE-2026-133968?
monailabel (PyPI): through 0.8.5.
Source: cve.now feed data
Am I affected, and how do I check?
MONAI Label from Project-MONIA through version 0.8.5 is listed as affected. The exposure depends on whether the server's PUT /datastore/image endpoint is reachable, and if authentication is enabled, whether the caller holds the ANNOTATOR role. Check the installed MONAI Label version and whether authentication is enabled on the server.
Source: github.com
How do I fix CVE-2026-133968?
The checked facts do not list a fixed version or vendor patch, so no upgrade target can be named. Check the vendor's advisory for a fix before relying on any version.
Source: github.com
What if there's no patch?
No fix is recorded in the checked facts. Limit access to the PUT /datastore/image endpoint to trusted callers, and if authentication is enabled, restrict the ANNOTATOR role to people who need it.
Source: github.com
Related
- CVE-2026-126255A path traversal: '../filedir' vulnerability in Fortinet FortiOS 8.0.0 through 8.0.1, FortiOS 7.6.0 through 7.6.7, FortiOS 7.4.0 through…
- CVE-2026-118485Axel Download Accelerator Path Traversal via URL Filename Decoding
- CVE-2026-66903Apache OFBiz: Authenticated Path Traversal in Catalog Image Management
- CVE-2026-133949pip bundles compromised eMudhra certificates via certifi
- CVE-2026-131167Unsafe usage of return values
- CVE-2026-131163Stored XSS in pretix-adyen
No corrections so far. Something wrong on this page? Report an error.