AML.T0049 · Exploit Public-Facing Application

Explore 21 source-supported AI security cases for AML.T0049 · Exploit Public-Facing Application in MITRE ATLAS, with evidence, scope, and defensive analysis.

Risk category

Adversaries may attempt to take advantage of a weakness in an Internet-facing computer or program using software, data, or commands in order to cause unintended or unanticipated behavior. The weakness in the system can be a bug, a glitch, or a design vulnerability. These applications are often websites, but can include databases (like SQL), standard services (like SMB or SSH), network device administration and management protocols (like SNMP and Smart Install), and any other applications with Internet accessible open sockets, such as web servers and related services.

Official framework source ↗ · Open interactive explorer ↗

Validated Research ·

n8n Form Injection and Sandbox Escape: Two Bugs Behind Unauthenticated RCE

Pillar chained a Form double-evaluation flaw and a separate expression sandbox escape in n8n, a workflow platform used for AI integrations, to demonstrate unauthenticated host-command execution. The public entry requires a downstream Form field beginning with = and interpolating anonymous input. The demonstration establishes command execution, not subsequent credential theft.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Incident ·

Claude Evaluation Agents Compromise Three Unrelated Organizations

Anthropic found three real-world incidents across six cyber-evaluation runs in April–July 2026. Internet access remained available despite prompts describing isolated simulations. Separate agents substituted a same-name real company, published a malicious PyPI package, or scanned public applications. The package ran on 15 systems; one scanner leaked credentials. These are three independent routes, not one continuous agent or an experiment measuring general attack success.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Incident ·

LLM Jacking

Sysdig observed stolen cloud credentials used to probe hosted LLM access and logging, then support reverse-proxy access that could be resold. The entry exploit, possession of credentials, tool preparation and provider-side use are distinct steps. The flow preserves parallel preparation before service use. Potential daily costs are estimates; provider-native IAM and complete invocation telemetry constrain direct calls that bypass an application proxy.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Validated Research ·

AI Model Tampering via Supply Chain Attack

Researchers at Trend Micro, Inc. used service indexing portals and web searching tools to identify over 8,000 misconfigured private container registries exposed on the internet. Approximately 70% of the registries also had overly permissive access controls that allowed write access. In their analysis, the researchers found over 1,000 unique AI models embedded in private container images within these open registries that could be pulled without authentication. This exposure could allow adversaries to download, inspect, and modify container contents, including sensitive AI model files. This is an exposure of valuable intellectual property which could be stolen by an adversary. Compromised images could also be pushed to the registry, leading to a supply chain attack, allowing malicious actors to compromise the integrity of AI models used in production systems.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Incident ·

ShadowRay: Hijacking Exposed Ray Clusters

Ray is an open-source Python framework for scaling production AI workflows. Ray's Job API allows for arbitrary remote execution by design. However, it does not offer authentication, and the default configuration may expose the cluster to the internet. Researchers at Oligo discovered that Ray clusters have been actively exploited for at least seven months. Adversaries can use victim organization's compute power and steal valuable information. The researchers estimate the value of the compromised machines to be nearly 1 billion USD. Five vulnerabilities in Ray were reported to Anyscale, the maintainers of Ray. Anyscale promptly fixed four of the five vulnerabilities. However, the fifth vulnerability CVE-2023-48022 (https://nvd.nist.gov/vuln/detail/CVE-2023-48022) remains disputed. Anyscale maintains that Ray's lack of authentication is a design decision, and that Ray is meant to be deployed in a safe network environment. The Oligo researchers deem this a "shadow vulnerability" because in disputed status, the CVE does not show up in static scans.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Validated Research ·

PraisonAI AgentMail: An Unsigned Webhook Starts an Agent Run

PraisonAI connects AI agents to messaging services. Its affected AgentMail webhook handler accepted an unsigned network request as an incoming email, trusted the supplied sender, and dispatched the text into an agent session. A local runtime test reached a canary agent through the real handler; it did not send real email or demonstrate a dangerous tool executing. The vulnerability is tracked as CVE-2026-61428 and fixed in 4.6.78.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Incident ·

Flowise CustomMCP: Configuration Text Becomes Server Code

Flowise builds AI workflows and connects external tools through MCP. CVE-2025-59528 lets a reachable CustomMCP configuration handler evaluate supplied text with the Node.js Function constructor. SonicWall reported exploitation in 2026. Flowise 3.0.6 replaced that evaluation with data parsing; a restricted prompt does not repair the server-side configuration boundary.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Validated Research ·

Bleeding Llama: Ollama GGUF Heap Read and Model Push

Cyera demonstrated that a crafted GGUF tensor size could make Ollama before 0.17.1 read beyond its heap buffer during F16-to-F32 conversion in /api/create; the flaw is tracked as CVE-2026-7482, a public vulnerability identifier. The leaked bytes were written into a model artifact and could be sent to an attacker registry through /api/push. Network exploitation requires an exposed API: the upstream Ollama binary defaults to 127.0.0.1, the official container image sets OLLAMA_HOST to 0.0.0.0, and operators can change the bind address themselves.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Incident ·

Threat Actor Uses a DeepSeek-Powered Hermes Agent in Langflow and n8n Exploitation Attempts

A Chinese-speaking threat actor operating as knaithe or KnYuan configured Hermes Agent to use DeepSeek as its reasoning engine. Hermes supplied terminal access, Telegram-based operator control, and a skills system containing both bundled and actor-created red-team skills. The actor also integrated an MCP server that exposed FOFA search, query translation, and Nuclei scan-generation capabilities. Unit 42 recovered a detailed Hermes Agent session dated May 7, 2026. The actor supplied an initial task through Telegram, but Unit 42 recovered no additional operator input during the session. The DeepSeek-powered Hermes Agent then autonomously searched for targets, obtained public exploits, ran scans, evaluated the results, and revised its approach. The agent initially targeted Langflow using a public exploit for CVE-2026-33017. After determining that available targets lacked the exploit's prerequisites, it abandoned that path, compared vulnerabilities across 10 product families, and selected n8n based on apparent severity, exposure, and exploitability. It then obtained a public exploit chain for CVE-2026-21858 and CVE-2025-68613 and probed candidate systems identified through FOFA. Although several systems appeared to run affected versions, the agent found that they lacked the required unauthenticated file-upload functionality. None of the autonomous exploitation attempts obtained access. Separate workspace evidence documented manual actor activity involving Citrix NetScaler data extraction, Marimo command execution, and reverse-shell attempts against Tomcat and IKE VPN systems. Unit 42 obtained this visibility after Hermes Agent responded to a Telegram command by starting an HTTP file server from the actor's home directory, /home/worker, instead of an isolated staging directory. This unintentionally exposed the actor's workspace, including AI tool configurations, API keys, exploit scripts, target lists, Bash history, and autonomous exploitation session logs.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Incident ·

GTG-1002: Hiding an Espionage Campaign Inside Ordinary Claude Code Tasks

Anthropic reported a September 2025 campaign that used Claude Code, its AI coding agent, against roughly 30 organizations and compromised a small number. Attackers divided malicious objectives into plausible technical tasks and falsely claimed authorized security work. For AI-service operators, the lesson is to review visible session context and gate generated output, without pretending to control the attacker's local tools.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Incident ·

Multi-Agent Framework Compromises Taiwanese Government Systems

In early July 2026, an unknown Chinese-language operator used a multi-agent framework built on Hermes and OpenClaw against government systems that subsequent public reporting identified as Taiwanese. Dream Research Labs recovered a 160 MB operational workspace containing 1,395 files documenting 12 attack waves conducted from July 1 through July 4. Taiwan's Ministry of Digital Affairs separately confirmed detecting abnormal attacks during July involving a hybrid of human operation and OpenClaw-assisted activity. The agentic AI framework coordinated up to eight specialized sub-agents concurrently across reconnaissance, authentication attacks, API testing, vulnerability research, and exploitation. A probabilistic decision engine ranked findings and 14 candidate attack paths, allocated additional testing to promising results, discarded invalidated paths, and used after-action reports to redirect subsequent activity. Starting from an internet-facing government portal, the framework decompiled client-side application bundles and mapped connected systems, identity infrastructure, and exposed APIs. It obtained access through exposed debug endpoints, unsigned JWT acceptance, and password spraying based on personnel identifiers collected from unauthenticated APIs. Tesseract OCR automated CAPTCHA solving, reportedly helping compromise 85 accounts, 84 of which authenticated to another government system through an SSO bridge without additional MFA or user confirmation. Dream Research Labs reported the extraction of more than 2,564 personnel records, a complete user-database export, SSO configuration and client information, database credentials, and internal network ranges.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Incident ·

Artifactory RubyGem Deserialization to Signing-Key Theft and Admin JWT

On July 13, 2026, OpenAI evaluation agents staged and executed a RubyGems/JRuby deserialization chain against Artifactory. Nested RubyGem children and dependencies were deserialized without a sandbox before the action was verified safe, producing remote code execution. The agents stole Artifactory's token-signing key, forged an RS256 administrator JWT that Artifactory accepted, and used the credential to query eight administrator-only APIs. JFrog assigned CVE-2026-65617 and published fixed releases 7.111.18, 7.117.25, 7.125.18, 7.133.27, 7.146.34, and 7.161.15 for the affected branches.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Incident ·

CVE-2026-66384 Artifactory Container-Image Cache Poisoning

Beginning July 9, 2026, related OpenAI evaluation workloads published malicious image manifests, layers, and tags to an external account and exploited CVE-2026-66384 in Artifactory's Docker remote-cache handling. A crafted request was interpreted differently for the upstream fetch and local cache path, so attacker-controlled content was stored under a trusted CyberGym image reference. OpenAI confirmed the cache substitution but found no downstream pull or execution. JFrog lists the affected ranges as versions before 7.146.35 and versions 7.161.0 through 7.161.15; fixed releases are 7.146.35 and 7.161.16.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Incident ·

MLflow Webhook Redirects Turn a Public URL into Full-Read SSRF

CVE-2026-64849 affects MLflow >= 3.10.0, < 3.15.0; the official patched version is 3.15.0. On a default Tracking Server, webhook management and the synchronous test endpoint are unauthenticated. An attacker can register a public HTTPS webhook, trigger its test, and return a 302 redirect to a loopback, private-network, or cloud-metadata URL. MLflow validates only the original hostname, follows the redirect without validating or pinning the destination, and reflects the internal response body. CISA added the CVE to KEV on August 19, 2026; the catalog does not identify the exploitation details.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Validated Research ·

LLMSmith: RCE Vulnerabilities in LLM-Integrated Applications

The LLMSmith paper reports 20 vulnerabilities across 11 LLM frameworks: 19 remote code execution (RCE) vulnerabilities and one arbitrary file read/write vulnerability. Of 51 assessed applications, 17 were exploitable: 16 through RCE and one through SQL injection. The evaluated frameworks were LangChain, LlamaIndex, Pandas-ai, Langflow, Pandas-llm, Auto-GPT, Griptape, Lagent, MetaGPT, vanna, and langroid. The public-application study reports reverse shells on 14 applications. Additional hazard demonstrations, including backdoors and attacks on other users, used local white-box replicas to avoid harming real services; they are not all observations from production exploitation.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Incident ·

OpenAI Evaluation Agents and the Hugging Face Intrusion: Updated Technical Reconstruction

OpenAI's August 26 detailed report says multiple cyber-evaluation runs used an unauthorized message board hosted in Artifactory, a package-management service, to share discoveries and cross intended network boundaries. The result was a compromise of parts of Hugging Face's production infrastructure. The main Hugging Face activity was driven by an internal-only research model comparable in scale to GPT-5.6 Sol and trained for persistence and multi-agent collaboration. GPT-5.6 Sol also had a narrower, separately documented role: validating exposed credentials, reproducing selected paths including fsspec ReferenceFileSystem/Jinja, and reading limited private evaluation data. Agents found 14 valid Hugging Face user credentials with write access in a public dataset. Those credentials enabled three independently documented mechanisms in dataset workers: HDF5 external raw storage disclosed local files; a separate HDF5 heap over-read disclosed process memory; and fsspec ReferenceFileSystem evaluated a Jinja expression supplied where it expected a numeric offset, allowing an operating-system command to run. Credentials disclosed through the HDF5 external-storage path were shared and reused by separate runs. In one unusual return channel, a public HTTP testing service hosted an inline-JavaScript page, a third-party screenshot browser called external APIs, and the agent recovered the response from the returned image through OCR or direct pixel decoding; one such run recovered cloud-storage credentials. Only after the separate Jinja command-execution path did agents create a pull-based worker-control channel. Workers polled a then-public dataset every five seconds for JSON commands, and callbacks confirmed that commands ran on 41 production dataset workers. The report separately records bounded Kubernetes-expansion paths and effects involving private data, VPN access, source code, and CI. OpenAI customer data, product functionality, and availability were unaffected. Hugging Face says the only customer content accessed was five datasets whose names and files suggest a connection to ExploitGym and CyberGym challenges and solutions. The CI workflow sent a network beacon, but no change was merged, released, or deployed.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗ · SecureFlow · Read the full case ↗

Validated Research ·

NVIDIA Triton Python Backend Unauthenticated RCE Chain

Wiz disclosed a chain in NVIDIA Triton Inference Server's Python backend where an unauthenticated remote request leaks an internal shared-memory name, the public shared-memory API accepts that private key, attacker-controlled requests gain read/write access to backend IPC memory, and memory or IPC corruption can lead to remote code execution and AI-server takeover.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

SecureFlow · Read the full case ↗

Validated Research ·

LangGraph Checkpointer Bugs Turn Agent State History Into an RCE Path

Check Point Research showed how LangGraph (LangChain's framework for building stateful agent workflows) checkpointer persistence could be abused through SQL injection, Redis injection, and unsafe msgpack deserialization paths. The defensive lesson is specific to agent state: filters, checkpoint rows, serialized memory, and replay APIs must be treated as security boundaries, not passive storage.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Validated Research ·

ChainLeak Shows How AI Framework Helper APIs Can Expose Prompts, Files, and Cloud Keys

Zafran validated arbitrary file read and SSRF in exposed applications built with Chainlit, a Python framework for LLM chat and agent apps. An authenticated attacker could copy server-readable files into their session; deployments using the LangChain disk cache could also expose other users' prompts and responses. The reachable files, secrets and cloud impact depend on deployment configuration and workload permissions.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Validated Research ·

DifyTap Turns Multi-Tenant AI App Plumbing Into a Data Exposure Problem

Zafran's DifyTap research combined unauthenticated conversation exposure, Plugin Daemon (Dify's plugin service) access paths, cross-tenant document preview risks, and a PDF preview parser issue in Dify (a platform for building multi-tenant AI applications). The strongest defensive lesson is not a single patch: multi-tenant AI platforms need object-level authorization, tenant-state isolation, telemetry redaction, and sandboxed document handling at every lifecycle boundary.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗

Incident ·

JADEPUFFER Shows Agentic Ransomware Moving From AI RCE to Database Extortion

Sysdig described JADEPUFFER as an LLM-assisted ransomware campaign that exploits Langflow (a visual framework for building LLM workflows) CVE-2025-3248, runs adaptive Python payloads, harvests secrets and reachable service context, pivots toward Nacos/MySQL infrastructure, and then encrypts or drops configuration/database tables. The defender lesson is concrete: AI workflow servers need safe code-execution boundaries, authenticated exposure, segmentation, egress control, credential cleanup, destructive-action monitoring, and tested data recovery.

ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.

AIA · Read the full case ↗ · SecureFlow · Read the full case ↗