Skip to main content
Incident intelligence/SS-IR-106CASE FILE OPEN
Symbolic editorial illustration for SS-IR-106SERVANTSTACK // INCIDENT INTELLIGENCEFORENSIC IMAGE // VERIFIED FRAME
SS-IR-106 // INCIDENT REPORTDocumented

Microsoft Copilot

Researchers Get the Assistant to Reveal Its Own Hidden Autorun Path, Then Demonstrate One-Click Data Theft and Persistent Memory Poisoning

EXECUTIVE BRIEF

On August 18, 2026, Varonis Threat Labs disclosed CoSnitch, an 8.8-rated Microsoft Copilot Personal vulnerability chain that could automatically execute a prompt from one crafted link, read data from connected services, exfiltrate it through Copilot's own URL-fetch behavior, and poison persistent memory. Microsoft patched CVE-2026-24301, and neither Varonis nor Microsoft reported known exploitation in the wild.

FAILURE CHAINTRACE COMPLETE
  1. 01TRIGGERVaronis disclosed CoSnitch after reporting the issue to Microsoft in December 2025 and coordinating through an…
  2. 02MACHINE ACTIONAutonomous actor
  3. 03MISSING GATERisk-based SME approval before execution
  4. 04IMPACTData security
01 // INCIDENT SUMMARY

The short version

On August 18, 2026, Varonis Threat Labs disclosed CoSnitch, an 8.8-rated Microsoft Copilot Personal vulnerability chain that could automatically execute a prompt from one crafted link, read data from connected services, exfiltrate it through Copilot's own URL-fetch behavior, and poison persistent memory. Microsoft patched CVE-2026-24301, and neither Varonis nor Microsoft reported known exploitation in the wild.

02 // KEY FACTS

Case telemetry

INCIDENT
SS-IR-106
DATE
August 18, 2026
SYSTEM
Microsoft Copilot
LOCATION / SCOPE
Microsoft Copilot Personal; global consumer service
EVIDENCE
Documented
AI ROLE
Autonomous actor
HARM
Data security
SOURCES
2 cited records
03ENTRY POINT // WHAT HAPPENED

The event

Varonis disclosed CoSnitch after reporting the issue to Microsoft in December 2025 and coordinating through an eight-month remediation period. Researchers first asked Copilot how automatic prompt execution could work; as they reframed each refusal, the assistant progressively described its URL behavior and eventually exposed an undocumented autorun parameter. A crafted Copilot URL could then execute the embedded prompt as soon as the page loaded, without a confirmation step after the victim opened the link. The prompt could query services already connected to that Copilot Personal session - including Gmail, Google Drive, Google Calendar, OneDrive, Copilot memory, and chat history - encode returned data into a URL, and make Copilot fetch an attacker-controlled destination. The trusted assistant became both the data reader and the outbound channel, making the traffic resemble its normal link-handling behavior. A separate indirect-prompt-injection path could place attacker instructions into Copilot's persistent memory when a user summarized a poisoned webpage; Varonis reported that the injected memory survived password changes, session revocation, and device re-enrollment until manually removed. Microsoft assigned CVE-2026-24301, rated it 8.8 under CVSS 3.1, and shipped server-side protections on August 18.

04CAUSAL TRACE // AI'S ACTUAL ROLE

What the machine did

Copilot did not develop malicious intent or independently select a victim. The causal AI role was privileged execution: the assistant treated attacker-supplied text as authenticated user instruction, invoked the victim's existing connectors, and used its own fetch capability to move the results outside the trusted session. Its conversational behavior also helped researchers discover the undocumented trigger by revealing architectural details while explaining why the proposed attack should not work. The incident is a responsibly disclosed vulnerability demonstration, not a confirmed customer breach, and the affected product was Copilot Personal rather than Microsoft 365 Copilot Enterprise.

Autonomous actorAutomation was a causal participant—not a decorative label for the system around it.
05BLAST RADIUS // CONSEQUENCES

Where the failure landed

Microsoft patched the vulnerability on August 18, and Varonis reported no evidence of exploitation outside its research. The demonstrated blast radius nevertheless included any personal email, file, calendar, chat, or memory source a user had already connected to Copilot Personal, plus durable manipulation of future assistant behavior through poisoned memory. CoSnitch was Varonis's third Copilot disclosure in 2026 after Reprompt and SearchLeak, reinforcing a recurring trust-boundary failure around prompt provenance, connector authority, and covert egress.

06 // EVIDENCE STATUS

Documented

Supported by Varonis's technical disclosure, Microsoft's CVE assignment and patch confirmation, and independent security reporting. The evidence establishes a researcher-demonstrated vulnerability in Copilot Personal, not exploitation in the wild or a known customer data breach.

SOURCE RECORD UPDATED 2026-08-18

07 // SOURCE LEDGER

2 cited records

  1. 01
  2. 02
08CONTROL FAILURE // MISSING GOVERNANCE

Risk-based SME approval before execution

The failure pattern in this case: High-stakes output had no accountable checkpoint.

09INTERVENTION POINT // HUMAN IN THE MIDDLE

The moment the path could change

The appropriate subject-matter expert reviews the evidence, exceptions, and affected people before the output becomes action.

AI PROPOSESHUMAN OWNS THE DECISIONSYSTEM EXECUTES
10CONTROL DEPLOYMENT // AUTHORITYGATE

Risk routing · named approval · audit trail

The product accepted a browser-loaded parameter as user intent, let untrusted webpage content become durable instruction, and allowed a privileged assistant to send connector-derived data to an arbitrary destination without a separate authorization event. AuthorityGate's Operational Resilience framework requires a named security SME to validate prompt provenance, connector scope, memory writes, and outbound destinations, with an independent approval gate before any externally supplied instruction can trigger access to connected data or persist across sessions. Connector calls should use task-scoped, short-lived authority; memory updates from external content should remain quarantined until reviewed; and data-bearing URL fetches should be blocked or explicitly approved rather than treated as routine assistant behavior.

RELEVANT KEYSTONE CONTROLHuman-in-the-Loop ValidationHow high-risk actions route to a named subject-matter expert who owns the go or no-go decision.
12 // THE ALTERNATIVE

Autonomy is a design choice.

See the operating model that keeps AI useful while preserving human authority at consequential moments.

Compare AgenticAI and AugmentedAI →