explainx.ai350K+ learn from us
TrendingAI News TodayExplainx for Business
Pricing
explainx.ai

Upskill in AI — 16 free pathways, live workshops & bootcamps, and 50+ courses from practitioners. Plus the skills, tools, and MCP servers to practice on.

follow us

follow on google

Add explainx.ai as a preferred source

corporate training

support@explainx.ai

get started

Find your pathTake Free Evaluation

community

Join the community

learn

mind: share how you thinkpathways — start freeworkshopsbootcampscoursescompare Explainxcertificationsmock testsexplainx universitycorporate traininglearn skills & mcp

discover

skillsmcp serversexplainx mcpestacktoolsmdx readeragentsllmsdesignsdictionarypeopleagi trackerfelony benchranks

company

aboutvisionmissionteaminstructorsteach on explainxpartnershipscommunityhackathonscareers

content

daily AI newsstate of AI — live resultsblogreleasespromptsgeneratorsresource libraryfor LLMsexplainx.ai kids

solutions

all solutionsdeveloper upskillingmarketing upskillingproduct manager upskillingleadership upskilling

newsletter · weekly

Get AI news, tools, and insights in your inbox.

supportcontactprivacytermsdata rightshow we create contentsubmission guidelines

© 2026 AISOLO Technologies Pvt Ltd

explainx.ai

On this page

  • TL;DR
  • How AWS discovered the campaign
  • When agents fail for hours, then win in minutes
  • The eleven-minute MONAI Label zero-day
  • Human operator re-enters after the zero-day
  • Attribution and parallel Cairn abuse
  • Actions AWS and maintainers took
  • Defender playbook for ML research stacks
  • How Cairn compares to other agent offense stories
  • What we cannot verify from AWS alone
  • What is CVE-2026-133968?
  • Why Redis and MONAI sat on the same campaign
  • Red-team versus real attacker economics
  • Clinical and research data boundaries
  • Related reading
← Back to blog

explainx / blog

AWS: Cairn AI Agents Found a MONAI Label Zero-Day in 11 Minutes

AI Security, AI Agents, AWS, MONAI, Cyberattacks

Part of AI Security

Amazon Threat Intelligence says China-nexus actors used Cairn autonomous agents to find an unpatched MONAI Label path traversal, then reach root on a university server. CVE-2026-133968, fixes, and defender playbook.

Nov 21, 2026·8 min read·Yash Thakker
add explainx.ai
go deep
AWS: Cairn AI Agents Found a MONAI Label Zero-Day in 11 Minutes

Amazon Threat Intelligence says a China-linked operator left a public Cairn autonomous pentest server on the internet, pointed agents at East Asian universities with the goal "obtain shell access," and watched them find an unpatched path traversal flaw in MONAI Label in about eleven minutes. In a follow-on session, the agents chained that bug to root on a medical-imaging server by planting a Python startup hook. AWS published the story on its Security Blog on November 20, 2026.

This is not the same October NorForge retail hacking report we covered from Reuters. AWS brings primary telemetry, MONAI Label specificity, and maintainer notification details defenders can act on today.

TL;DR

table · 2 cols
ItemDetail (per AWS Nov 20 post)
ToolCairn open-source autonomous AI pentest framework
ExposureOperator left Cairn UI without authentication
Victim appMONAI Label medical imaging annotation server
BugPath traversal on upload endpoints; no CVE at time of exploit
Speed~11 minutes from API mapping to arbitrary file write
Rootsitecustomize.py plus training endpoint spawning Python as root
AdvisoryGHSA-qc22-rmgc-vg94; fix merged, no release yet
Daily briefFrom Yash · 350K+ students taught

Catch up on AI

One AI story explained in plain English, plus one thing to try. Every day, free. Unsubscribe anytime.

How AWS discovered the campaign

On September 10, 2026, Amazon Threat Intelligence spotted a server hosting Cairn without login. Because the instance was public, outsiders could read project configs, actor prompts, and agent output. Prompts were in Simplified Chinese; script timestamps used China Standard Time.

The visible campaign targeted university IP addresses in East Asia outside mainland China for roughly 48 hours starting September 8, 2026. AWS published two indicators of compromise IPv4 addresses (partially redacted in the post) from that window.

Cairn's design is straightforward: you give a starting point and a plain-language objective, and multiple agents plan, execute, and adapt without the operator clicking each step. AWS stresses the same UX that helps defenders also helps attackers who can pay model bills.

When agents fail for hours, then win in minutes

Circular scan frame with a green highlight spot suggesting automated reconnaissanceCircular scan frame with a green highlight spot suggesting automated reconnaissance

AWS highlights two failed long runs to show persistence:

Hardened Redis at one university

Against an unauthenticated Redis instance, agents spent about 16 hours across 148 sequential actions. They tried replication abuse, sandbox escape, config writes, memory corruption, and even Log4Shell attempts against a co-located service. They also used SSRF through a Qdrant instance to map Docker networks and sprayed credentials against PostgreSQL, SSH, and other services. None succeeded.

GPU server credential spraying

Another operation ran 6+ hours on a GPU server. Agents harvested roughly 80 usernames from public faculty pages, papers, and lab sites, then tried 30,000+ password combinations against SSH, an admin dashboard, storage, VPN, and a campus portal. No working login.

Those failures matter: they show agents iterate like junior pentesters with unlimited stamina. The breakthrough came on a soft target: an internet-reachable MONAI Label install with default-style exposure.

The eleven-minute MONAI Label zero-day

Green lens highlights a spot on a stylized medical imaging ribcage outlineGreen lens highlights a spot on a stylized medical imaging ribcage outline

AWS says agents identified the framework, mapped API endpoints, and focused on an upload route with a filename parameter. Path traversal tests succeeded. AWS assesses with high confidence this was a zero-day because no fix, issue, or database entry existed yet for the project.

The GitHub advisory now tracks the flaw:

  • Endpoints PUT /datastore/image and PUT /datastore/label join a caller-controlled ID onto storage paths without keeping writes inside the datastore.
  • MONAI_LABEL_AUTH_ENABLE=False by default, so any network client that can reach the port may trigger writes.
  • Versions 0.8.5 and earlier are affected.
  • Fix logic landed in pull request #1915, merged October 19, 2026, but patched versions: None on the advisory as of November 18, 2026.

Root shell in a later session

Eleven minutes bought arbitrary file write. Root came later when agents:

  1. Wrote a reverse shell into sitecustomize.py (auto-imported by Python).
  2. Called a training API endpoint to spawn a fresh Python process.
  3. Watched that process import the payload and connect back as root.

AWS does not claim patient scans were exfiltrated. It does show machine learning research infrastructure can become a code execution bridge when auth and network controls are loose.

Human operator re-enters after the zero-day

In another session, AWS says a human stepped in after the agents found the bug. The operator supplied a proxy tunnel into a second university network where the same vulnerable software ran, suggesting manual reuse of the exploit to pivot. Agents then explored additional hosts through that tunnel.

That pattern matches how offensive teams may use agents for breadth and humans for lateral movement once a repeatable exploit exists.

Attribution and parallel Cairn abuse

AWS attributes the campaign with moderate confidence to a China-nexus actor, citing language, timestamps, and university targeting. It does not map the activity to a named APT.

The post also cites Gambit Security research on a financially motivated actor using Cairn against online retailers, underscoring that Cairn adoption is not limited to espionage. Our earlier Reuters-based Cairn retail story covered different victims but the same framework family.

For a wider agent-misuse index, see explainx.ai's running felony-bench tracker of agents affecting real third parties.

Actions AWS and maintainers took

AWS says it notified MONAI Label maintainers, who published a fix path and GitHub advisory. Victim universities were not AWS customers, so AWS worked through a government partner to alert them.

Behind the scenes, AWS highlights honeypots and network-level restrictions on scanning activity. That is infrastructure-level defense, not a substitute for patching research software you expose.

Defender playbook for ML research stacks

Shield with a hairline crack under a green security patchShield with a hairline crack under a green security patch

Network and auth defaults

MONAI Label is built for trusted lab networks, not open internet edges. Until a patched package ships:

  • Set MONAI_LABEL_AUTH_ENABLE=True and limit ANNOTATOR roles.
  • Block public ingress; require VPN or private links.
  • Run the service account with minimal write permissions outside the datastore.

Speed assumptions

AWS argues SOC timelines tuned for human attackers lag autonomous agents that never pause. Pair high-confidence detections with automated containment, with humans reviewing outcomes instead of every single tool call.

Coding agents that can hit ML admin APIs need outbound controls. AgentBeam can block dangerous agent actions before they reach exposed research endpoints.

Patch tracking

Watch GHSA-qc22-rmgc-vg94 and the MONAI Label release page. A merged fix on main is not the same as a version your orchestrator can pull.

How Cairn compares to other agent offense stories

table · 2 cols
IncidentWhat differed
NorForge retail campaign (Oct)Journalist-sourced, e-commerce focus, mixed models
AWS MONAI case (Nov)Primary AWS blog, medical ML stack, measured 11-minute zero-day window
OpenAI CI root misalignment reportBenign eval agents misusing peer credentials

What we cannot verify from AWS alone

AWS describes its reconstruction from a public Cairn instance. Independent media have not re-tested the MONAI exploit chain. Clinical impact (PHI exposure) is not claimed.

Treat root on one server as a warning for any default-open MONAI Label on your perimeter, not proof every install falls the same way.

What is CVE-2026-133968?

Outlets including The Hacker News report that the MONAI Label flaw now carries CVE-2026-133968 with a 9.8 critical CVSS score. The GitHub advisory timeline still shows patched versions: None while maintainers prepare a release. Treat the CVE as the tracking ID for scanners even if your package manager cannot upgrade yet.

Workarounds from the advisory

Until you can install a fixed release, MONAI Label's advisory recommends:

  • Enabling authentication and withholding ANNOTATOR from untrusted users.
  • Keeping the server off public networks.
  • Running the process as an unprivileged user with writes limited to the datastore tree.

Those controls would not stop a determined insider, but they block the anonymous network client path AWS describes.

Why Redis and MONAI sat on the same campaign

The Redis stretch matters for defenders who think "we patched Redis years ago." AWS documents 148 distinct attempts against a misconfigured instance. Agents treated failure as signal, not stop. Only when they found a web-facing ML admin API with permissive uploads did the timeline collapse to minutes.

If your org runs research GPUs and legacy data stores on overlapping subnets, segment them. Agents chaining SSRF from Qdrant to internal PostgreSQL shows how graph-like exploration crosses service boundaries humans forget to firewall.

Red-team versus real attacker economics

Cairn's README celebrates defender use in hackathons. AWS and Gambit show the same UI on a VPS with a stolen API key budget. Your red team using Cairn with authorization is legitimate; an exposed Cairn dashboard without auth is a live operation journal for threat hunters.

Document that difference in policy: pentest agents belong in isolated VPCs, not port 443 on a default cloud image.

Clinical and research data boundaries

MONAI Label often sits near imaging pipelines that are not HIPAA production systems but still hold identifiable research scans. AWS does not claim imaging theft in this post. The lesson is architectural: labeling servers are production-adjacent and attract agents scanning university IP space.

Pair this incident with ECHR lawyer sanctions for AI-hallucinated citations as another reason research IT cannot treat ML tooling as "lab only" without network controls.

Related reading

  • November 2026 cyberattacks tracker
  • FBI flash warning on agentic AI attacks
  • Cloudflare ARTEX and pentest orchestrators
  • Dragos AI supply chain canary research
  • Vercel agent-browser accessibility-tree harness
Spotted something out of date? Let us know.
Daily briefFrom Yash · 350K+ students taught

Catch up on AI

One AI story explained in plain English, plus one thing to try. Every day, free. Unsubscribe anytime.

  • ✓ Free
  • ✓ One email a day, no spam
  • ✓ Unsubscribe anytime
Yash Thakker

Written by

Yash Thakker

Yash is an AI expert with over 300K learners. Join his workshops →

View Yash Thakker in People in AI →

Related posts

Nov 19, 2026

Skyflow on AgentCore Gateway: Keep Sensitive Data Out of Agent Tool Calls

A November 19, 2026 AWS post shows how Skyflow Detect plugs into Amazon Bedrock AgentCore Gateway as a request and response interceptor. It tokenizes names and card numbers before tools or models see them, and swaps documents for clean copies. Here is how the three modes work and what is still preview.

Nov 6, 2026

Okta Cross App Access and AgentCore Gateway: Governing AI Agents at Scale (Part 2)

Part 2 of the AWS and Okta series swaps per-server checks for one AgentCore Gateway front door with default-deny Cedar policy, adds a second agent on EKS, and traces every allow and deny. Here is the design, the test results, and the caveats.

Oct 19, 2026

One Hacker, AI Agents and About $5,000: How Deere, SharkNinja and Cummins Sites Were Breached

Reuters reports that a Chinese-speaking hacker used commercially available AI agents to attack more than 1,200 websites and break into over 100 organizations, including Deere, SharkNinja and Cummins, for roughly $5,000 in tokens. Here is what the researcher found, what the companies said, and what remains unknown.