Explore 9 source-supported AI security cases for AML.T0107 · Exploitation for Defense Evasion in MITRE ATLAS, with evidence, scope, and defensive analysis.
Risk category
Adversaries may exploit a system or application vulnerability to bypass security features. Exploitation of a vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Vulnerabilities may exist in defensive security software that can be used to disable or circumvent them.
Rebora disclosed two different browser-extension privilege crossings. Spyder abused Sider's synthetic drag and cross-origin gesture path to drive an authenticated Gemini page; MaXSS sent a forged page message through MaxAI's content script to a generic privileged background-function bridge. Rebora counted about 11 million Chrome and Edge installations across both products at publication, but the two mechanisms and their remediation status must be reviewed separately.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.
Varonis showed that update rights on one Dialogflow CX agent could be converted into persistent control of a Google-managed Cloud Run execution environment shared by other agents in the project. A Playbook Code Block overwrote code_execution_env.py , after which the modified runtime could intercept conversations, alter live replies, exfiltrate data, and query instance metadata. Google fully remediated the affected components in June 2026.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.
A computer-use agent selected a benign Continue button from a screenshot, paused to reason, and later clicked the same coordinates after the page had replaced that control with Outlook's Send button. The resulting email was written by the attacker. The case turns a familiar time-of-check to time-of-use race into a browser-agent problem: the observed screen cannot authorize a later action unless the target is revalidated immediately before the click.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.
DuneSlide exposed two independent Cursor 2.x flaws. An indirect prompt injection could make the agent authorize an out-of-project working directory, or exploit a fail-open symlink check in the Write tool. Either route could overwrite Cursor's sandbox helper so a later command ran without the intended terminal sandbox. Cursor 3.0 fixed both issues and had already shipped on April 2, three months before Cato's public article.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.
CVE-2025-62593 affects Ray before 2.52.0. A developer running the Ray Dashboard on its default port can be compromised after visiting a malicious page or advertisement in Firefox or Safari. DNS rebinding changes the attacker's origin to the local or private Ray endpoint; browser JavaScript sets a non-Mozilla User-Agent to bypass Ray's weak browser heuristic, then submits a job to the unauthenticated Jobs API. Ray executes the supplied command. CISA added the CVE to KEV on August 17, 2026, but has not attributed the exploitation.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.
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.
CVE-2026-70477 affects Flowise and flowise-components through 3.1.2 and is fixed in 3.1.3. In the disclosed prompt-injection path, an unauthenticated attacker sends instructions to a chatflow containing a CSV Agent. The LLM returns obfuscated Python, the static regex blocklist accepts it, and Flowise passes the code to Pyodide. Because that runtime was not isolated from host operating-system interfaces, the payload executes with the privileges of the user running the server.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.
Microsoft documented two distinct Semantic Kernel prompt-to-host-RCE paths: a Python Search Plugin filter evaluated with eval(), and a .NET SessionsPythonPlugin file-transfer function exposed to model tool calling that could write a payload into the host Startup folder.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.
Oasis Security showed in its early-2026 tests that a malicious website could open a WebSocket to OpenClaw's localhost gateway (the local management entry point for an agent platform), skip origin checks by claiming a CLI client, then brute-force password auth because loopback attempts were exempt from rate limits. The fix is already out; the lesson is to stop treating localhost as identity and to scope every agent session and RPC method as privileged.
ATLAS annotations follow the source SecureFlow steps; they are not a MITRE endorsement of cross-framework mappings.