7 · Sabotage / Integrity Degradation

Explore 12 source-supported AI security cases for 7 · Sabotage / Integrity Degradation in Cisco AI Security & Safety Framework v2.0, with evidence, scope, and defensive analysis.

Risk category

An attacker corrupts a model or agent's planning, reasoning, decisions, or supporting information to produce harmful results. Cisco includes reasoning corruption, immediate memory corruption, manipulation of external data sources, and misuse of model-specific or security tokens. The system can then make an incorrect judgment or select an unsafe action, even when the malicious influence entered through a supporting component rather than the reasoning prompt itself.

Official framework source ↗ · Open interactive explorer ↗

Validated Research ·

LiteLLM CVE-2026-89032: Broken Semantic-Cache Isolation Enables Cross-User Leaks and Tool-Call Poisoning

LiteLLM is a gateway that routes applications' requests to language models. Its semantic cache can reuse an earlier answer when two questions have similar meanings. NVISO showed that in the tested configuration, /v1/responses reused cached entries across different API keys. This exposed simulated support data and allowed a fabricated answer or tool-call response to reach a different user. The researchers also demonstrated downstream execution in a mock banking tool and the pi coding agent. CVE-2026-89032 was fixed in v1.101.0-rc.1.

Why it relates: A poisoned stored response induced incorrect later answers and altered a proposed tool operation.

All downstream consequences are from separate tests against the vulnerable cache behavior.

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

Exercise ·

Lazarus: A Small Weight Edit Can Hide a Triggered Agent Payload

Lazarus explores backdoors planted by editing a small part of an open-weight model. The critical prerequisite is control of the checkpoint that a defender later accepts. Its results support stronger model intake and tool containment, while the paper’s different prediction and execution measurements must remain distinct.

Why it relates: The modified neurons corrupt agent behavior under selected conditions without broadly destroying utility.

Only the main executed marker path supports execution claims; action-format prediction measurements retain their narrower scope.

AIA · Read the full case ↗

Exercise ·

Trained to Betray: Poisoned Data and Checkpoints Redirect Coding Agents

Microsoft reports two controlled post-training attacks: a victim fine-tunes on poisoned agent trajectories, or adopts an attacker-trained checkpoint. Ordinary requests or repository context then trigger unsafe, schema-valid tool calls. Kerkoporta uses supervised fine-tuning followed by reinforcement learning to recover useful coding performance while retaining the backdoor. Neither study establishes a malicious customer breach or a defect in stock coding-agent configurations.

Why it relates: The planted behavior corrupts task and tool selection while preserving much ordinary utility.

Dataset and checkpoint experiments remain separate; tool-call acceptance, actual execution and production compromise are not interchangeable.

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

Validated Research ·

AgentCorruption: A Stolen Execution Role Turns Memory into Persistent C2

Zenity tested an AWS Bedrock AgentCore deployment, a managed environment for running AI agents, with a network-capable agent and a broad execution role. The agent relayed temporary role credentials from its metadata endpoint. Off-platform API calls then reached other memories and agents. The distinctive persistence path wrote short-term conversation events that configured extraction strategies could turn into long-term records; later retrieval directed the agent to a mutable command page. The reach was demonstrated within an account and region, not as a microVM escape or automatic cross-account compromise. The researchers observed major default-role restrictions on September 29; existing deployed roles still require independent inspection.

Why it relates: Forged events corrupt the information used for later agent decisions.

Controlled broad-role AgentCore deployment with separate direct API and retained-memory/C2 branches; account/region scope, tool prerequisites and later default-role restrictions remain explicit.

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

Validated Research ·

SSMS Copilot: Database Instructions Turn Read-Only Tools into SYSADMIN

Johann Rehberger tested Copilot, the AI query assistant in SQL Server Management Studio (SSMS), and made a database owner's stored instructions induce execution under another user's more privileged SQL connection. A regex-based read-only check failed to contain dynamic SQL, and the final demonstration added the attacker's login to sysadmin. Separate direct-prompt experiments sent table data over SMB; these are distinct demonstrations, not evidence of a single observed intrusion.

Why it relates: Tampered supporting information corrupts the assistant's reasoning about which SQL operations to perform.

Controlled SSMS metadata-to-SQL escalation plus separate direct SQL/SMB tests; no joined intrusion or OS escape is asserted.

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

Incident ·

AI Recommendation Poisoning: Summary Links That Try to Rewrite Assistant Memory

Microsoft found companies using AI summary links to plant promotional instructions in assistants with persistent memory, a feature that retains preferences across conversations. If accepted and later recalled, those instructions can influence recommendations long after the original page is closed. The defensive priority is to keep website-authored requests from silently becoming trusted user preferences.

Why it relates: Microsoft reported real-world attempts to influence AI recommendations through links presented as summarization tools. The relevant category is Sabotage / Integrity Degradation: An attacker corrupts a model or agent's planning, reasoning, decisions, or supporting information to produce harmful results. Directly submitted link text may be accepted into durable memory and bias later recommendations, conditional on successful memory write and recall.

Microsoft reported real-world attempts to influence AI recommendations through links presented as summarization tools. Website operators placed promotional instructions in URL prompt parameters that open an AI assistant. If the assistant accepts those instructions as durable memory, later answers can favor the operator's brand or website. The report identifies more than 50 unique prompts associated with 31 companies across 14 industries; these are attempts, not a count of successful compromises. Effectiveness varies by platform and over time. Its fictional brands and financial-loss examples illustrate possible consequences. The six-step flow follows ATLAS's ordered procedures; the last two steps depend on successful memory acceptance and subsequent recall.

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

Research ·

SkillJack Turns Poisoned Agent Experience Into a Reusable Skill

The SkillJack paper evaluates SkillX and Anything2Skill, which transform agent experience trajectories into reusable skills. In a synthetic AppWorld study using one DeepSeek-v4-flash API, poisoned trajectories survived the transformation and evaded the evaluated routing-level detectors, with reported persistence after source records were deleted. This is a controlled research result, not a demonstrated compromise of a production skill registry or external service.

Why it relates: The SkillJack paper evaluates SkillX and Anything2Skill, which transform agent experience trajectories into reusable skills. The relevant category is Sabotage / Integrity Degradation: An attacker corrupts a model or agent's planning, reasoning, decisions, or supporting information to produce harmful results.

The SkillJack paper evaluates SkillX and Anything2Skill, which transform agent experience trajectories into reusable skills. In a synthetic AppWorld study using one DeepSeek-v4-flash API, poisoned trajectories survived the transformation and evaded the evaluated routing-level detectors, with reported persistence after source records were deleted. The work is a controlled research result, not a demonstrated compromise of a real organization's skill registry or external service.

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

Validated Research ·

CoSnitch Combined Copilot Autorun Exfiltration with a Separate Memory-Poisoning Path

CoSnitch covered two independent Copilot attacks. A crafted copilot.microsoft.com link combined ?q= with an undocumented autorun=1 parameter, causing an authenticated session to run an embedded prompt without confirmation and send connected data through URL fetches. Separately, hidden instructions in a webpage summarized by Copilot invoked memory.add and persisted in long-term memory. Microsoft fixed CVE-2026-24301 on August 18.

Why it relates: When Copilot summarized an attacker-controlled webpage, hidden instructions were parsed as a higher-authority directive and invoked memory.add with attacker-controlled content. The relevant category is Sabotage / Integrity Degradation: An attacker corrupts a model or agent's planning, reasoning, decisions, or supporting information to produce harmful results.

When Copilot summarized an attacker-controlled webpage, hidden instructions were parsed as a higher-authority directive and invoked memory.add with attacker-controlled content. The resulting long-term memory survived password changes, session revocation, and device re-enrollment until explicit removal, and could be recalled into later conversations. Varonis states that Microsoft shipped patches on August 18, 2026. A crafted copilot.microsoft.com link combined attacker instructions in q with the undocumented autorun=1 parameter. In an authenticated browser session, Copilot submitted the prompt without a separate confirmation, retrieved data from connected services or prior conversations, encoded selected values into an attacker URL, and fetched it. Microsoft shipped patches on August 18, 2026.

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

Research ·

MCFA Turns Agent Memory into a Delayed Control-Flow Input

Memory Control Flow Attacks (MCFA) do not need direct access to an agent's memory database or system prompt. The research shows how ordinary interaction can place an action-oriented preference into long-term memory, then a later benign task retrieves it and changes tool choice or order. Across controlled LangChain and LlamaIndex experiments, tool-selection attacks were highly reliable, while ordering attacks were weaker. Memory must therefore be governed as persistent control input, not trusted conversation history.

Why it relates: Memory Control Flow Attacks (MCFA) do not need direct access to an agent's memory database or system prompt. The relevant category is Sabotage / Integrity Degradation: An attacker corrupts a model or agent's planning, reasoning, decisions, or supporting information to produce harmful results.

Memory Control Flow Attacks (MCFA) do not need direct access to an agent's memory database or system prompt. The research shows how ordinary interaction can place an action-oriented preference into long-term memory, then a later benign task retrieves it and changes tool choice or order. Across controlled LangChain and LlamaIndex experiments, tool-selection attacks were highly reliable, while ordering attacks were weaker. Memory must therefore be governed as persistent control input, not trusted conversation history. The attacker did not need memory-database access. One or a few ordinary interactions caused the agent to store an action-oriented preference. A later benign task retrieved it and changed tool choice or order, while the trusted tools and system prompt remained unchanged. The study measured related but distinct outcomes. Override selected a risky tool and reached 97.2% to 100% success. Order violated a required sequence and reached 52.8% to 69.4%. Cross-task and more-than-30-round tests showed that the effect could persist, while matched benign-memory controls remained at 0%. Simple mitigations were incomplete. Adding 100 benign records did not remove the effect. Summarization reduced malicious-write success, but every summarized instruction that survived still steered the later task. Role-based memory segregation reduced some Override rates, yet residual success ranged from 2.8% to 100%. This was controlled research. The evaluation used synthetic safe and risky tool variants, no production users, and no harmful external actions. It measured tool-trace deviation, not real damage. There is currently no public evidence that MCFA has been used in an actual attack.

AIA · Read the full case ↗

Validated Research ·

Hacking ChatGPT's Memories with Prompt Injection

Embrace the Red (https://embracethered.com/blog/) demonstrated that ChatGPT's memory feature is vulnerable to manipulation via prompt injections. To execute the attack, the researcher hid a prompt injection in a shared Google Doc. When a user references the document, its contents is placed into ChatGPT's context via the Connected App feature, and the prompt is executed, poisoning the memory with false facts. The researcher demonstrated that these injected memories persist across chat sessions. Additionally, since the prompt injection payload is introduced through shared resources, this leaves others vulnerable to the same attack and maintains persistence on the system.

Why it relates: Embrace the Red (https://embracethered.com/blog/) demonstrated that ChatGPT's memory feature is vulnerable to manipulation via prompt injections. The relevant category is Sabotage / Integrity Degradation: An attacker corrupts a model or agent's planning, reasoning, decisions, or supporting information to produce harmful results.

Embrace the Red (https://embracethered.com/blog/) demonstrated that ChatGPT's memory feature is vulnerable to manipulation via prompt injections. To execute the attack, the researcher hid a prompt injection in a shared Google Doc. When a user references the document, its contents is placed into ChatGPT's context via the Connected App feature, and the prompt is executed, poisoning the memory with false facts. The researcher demonstrated that these injected memories persist across chat sessions. Additionally, since the prompt injection payload is introduced through shared resources, this leaves others vulnerable to the same attack and maintains persistence on the system.

SecureFlow · Read the full case ↗

Validated Research ·

Copirate 365: Persistent Memory-Backdoor Data Exfiltration in Microsoft 365 Copilot (CVE-2026-24299)

A validated research flow showing how a poisoned document, Delayed Tool Invocation, and a record_memory write build a persistent Microsoft 365 Copilot backdoor that exfiltrates pasted secrets every future session through a CSS font-face URL that evades the image-src CSP.

Why it relates: A validated research flow showing how a poisoned document, Delayed Tool Invocation, and a record_memory write build a persistent Microsoft 365 Copilot backdoor that exfiltrates pasted secrets every future session through a CSS font-face URL that evades the image-src CSP. The relevant category is Sabotage / Integrity Degradation: An attacker corrupts a model or agent's planning, reasoning, decisions, or supporting information to produce harmful results.

A validated research flow showing how a poisoned document, Delayed Tool Invocation, and a record_memory write build a persistent Microsoft 365 Copilot backdoor that exfiltrates pasted secrets every future session through a CSS font-face URL that evades the image-src CSP.

SecureFlow · Read the full case ↗

Validated Research ·

OpenClaw Command & Control via Prompt Injection

A curated AI-agent incident flow showing indirect prompt injection, malicious tool invocation, persistent agent configuration poisoning, and command-and-control behavior.

Why it relates: A curated AI-agent incident flow showing indirect prompt injection, malicious tool invocation, persistent agent configuration poisoning, and command-and-control behavior. The relevant category is Sabotage / Integrity Degradation: An attacker corrupts a model or agent's planning, reasoning, decisions, or supporting information to produce harmful results.

A curated AI-agent incident flow showing indirect prompt injection, malicious tool invocation, persistent agent configuration poisoning, and command-and-control behavior.

SecureFlow · Read the full case ↗