On 20 November 2026 Amazon Threat Intelligence reported that a threat actor's Cairn AI agents found and exploited a zero-day in MONAI Label, an open-source server for AI-assisted annotation of medical images. A monitoring brief sent to VSO described the case as one where the agents' behaviour was a black box that could not be reconstructed. We checked it against the primary sources and registered it as V1120MONAILABEL. These are the engineering notes.
sitecustomize.py. The agents then call a training endpoint, which starts a new Python process. The interpreter loads Attribution is Chinese-nexus with moderate confidence (Simplified Chinese prompts, China Standard Time timestamps, targeting). Zero-day status is assessed with high confidence. The models behind the agents are not named.
The CVE record (CVE-2026-133968, CNA MITRE, published 2026-11-20) describes directory traversal via the image parameter of PUT /datastore/image in MONAI Label through 0.8.5, CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N), CWE-24. Two oddities if you consume CVE JSON automatically: the vendor is spelled Project-MONIA, and the CISA ADP enrichment lists Exploitation: none while the description says the flaw was exploited in the wild from September 2026.
From the repository:
monailabel/config.py sets MONAI_LABEL_AUTH_ENABLE: bool = False. An instance started with defaults accepts unauthenticated requests.113527b (PR #1915, merged 2026-10-19), "fix: confine datastore write paths", resolves each destination and requires it to stay inside the datastore's image and label directories, and strips directory components from the image ID at the upload endpoint.af39c0c (2026-11-19) adds a README warning: MONAI Label is not intended to be internet-facing, has known unpatched issues, and should run only on a closed, trusted LAN.monailabel release is still 0.8.5 (2024-11-25), and the repository's latest tag is 0.8.5. Amazon's post says the maintainers released a fix; as of 22 November the fix exists only in the source.
So for anyone running MONAI Label: the published package does not contain the fix, and the maintainers' own guidance is to keep the server off the internet.
Cairn's agents write findings and intentions to a shared record as they work. Left unauthenticated, that record became the evidence. It is also the third time Cairn appears in the VSO registry: exposed Cairn panels hijacked by third parties (V1026CAIRN), and tooling that identified itself as Cairn behind the unauthorised agent-framework releases on PyPI (V1117AGENTFRAMEWORK).
The engineering lesson is not "keep more logs". The attacker kept excellent logs. The problems are:
VAP places no obligation on an attacker's tools, so it says nothing about the Cairn instance. On the defenders' side, the exploited path was an upload endpoint, not an AI decision, and VAP is not a general-purpose logging framework (§1.3). The medical profile, MAP, is a v0.1.2 Working Draft, not for production conformance claims (§4.5.2). Where VAP is implemented, records are tamper-evident and post-anchor omission is detectable at anchor granularity (INT-008); events never recorded or never anchored before a compromise are out of reach. Agent tool-invocation records are the subject of DAP, a v0.1.0 Working Draft (§4.6.2). VAP has no monitoring or intervention role (§4.4.4).
It would not have detected or stopped the exploitation, fixed the traversal, changed the auth default, identified the operator, recorded the agents' reasoning, or recovered unrecorded events on the compromised servers.
"does not warrant the correctness, fairness, or safety of the underlying AI decisions — only the integrity, completeness (at anchor granularity), and attributability of their records." (VAP v1.2 §1.6(c))
The brief's second item, California's complaint against OpenAI (V1116CAAG), brought no new primary facts and is not recorded again.
Latest published count, dated 25 October 2026: zero external implementations of VAP or any VAP profile; zero Evidence Packs accepted in any proceeding. A previously published contract figure was withdrawn on 24 October 2026; the withdrawal does not establish a count of zero. VAP has no standing within the IETF, ISO/IEC JTC 1/SC 42, ITU-T or any other established standards body. VSO's operating base is VeritasChain Co., Ltd.; VSO develops VAP and has an interest in how it is described. Verification and drafting were done with Claude, made by Anthropic.