CVECVE-2026-24301
CVSS 8.8
NameCoSnitch
(Varonis)
PatchedAugust 18, 2026
(8 months post-report)
ScopeCopilot Personal only
copilot.microsoft.com
M365 Copilot
not affected
ExploitationNot confirmed
in wild
What happened
Varonis Threat Labs disclosed CoSnitch on August 18, 2026, the same day Microsoft shipped the fix. Researcher Lior Adar reported the vulnerability chain to Microsoft in December 2025. The disclosure came nearly eight months later. CoSnitch chains three separate weaknesses in Microsoft Copilot Personal, the consumer AI assistant hosted at copilot.microsoft.com. The first weakness is automatic prompt execution: the standard ?q= URL parameter for pre-populating a Copilot query can be combined with a second, undocumented parameter, which Varonis identifies as ?autorun=1 in its technical write-up, to cause Copilot to execute the embedded prompt instantly when the page loads rather than waiting for the user to press Enter. An attacker sends a victim a link that looks like a normal Copilot URL. When the victim clicks the link and Copilot loads, the attacker's prompt fires automatically in the context of the victim's authenticated session. The second weakness is OAuth-scoped data access: Copilot Personal can be connected to Gmail, Google Drive, Google Calendar, and other services through OAuth integrations. A prompt running in the victim's authenticated session can read data from any of those connected sources as if the user had asked Copilot to retrieve it. The third weakness is the exfiltration path: Copilot has a capability to fetch and summarize external URLs. An attacker-controlled prompt can gather data from connected accounts into the model's active context, encode it for URL transport, and instruct Copilot to request an attacker-controlled URL containing the encoded information. The response, including email content, calendar entries, file metadata, chat history, and persistent memory contents, arrives at the attacker's server through what appears to be a routine Copilot summarization request. Varonis confirmed that the entire attack chain produces no process, file, network connection, or log entry that standard security tooling would flag as anomalous. The exfiltration is indistinguishable from normal Copilot behavior. Microsoft assigned CVSS 8.8, rated it a critical information disclosure vulnerability, and noted no customer action is required following the August 18 patch. Enterprise customers using Microsoft 365 Copilot are unaffected. The scope is limited to Copilot Personal. Varonis confirmed no evidence of exploitation in the wild before the patch.
Why it matters
CoSnitch is the third Copilot vulnerability Varonis disclosed this year, following Reprompt, which bypassed safety guardrails by repeating a question, and SearchLeak, which turned Microsoft 365 Copilot Enterprise into a silent exfiltration channel. All three share the same attack pattern: one click on a link that looks ordinary triggers a chain the victim cannot observe, producing data exfiltration that looks like normal assistant activity. The operational concern for enterprise security teams is not only that Copilot Personal was exploitable. It is that the pattern Varonis identified, automatic prompt execution through a crafted URL followed by OAuth-scoped data access and exfiltration through a routine assistant capability, is not unique to Copilot. Any AI assistant that accepts prompts through URL parameters, has broad OAuth access to connected services, and can reach external URLs as part of its normal function has the same structural attack surface. The meta-hacking discovery method Varonis used, repeatedly asking Copilot why automatic prompt execution was supposedly impossible until it surfaced the mechanism, is additionally significant: the researchers did not reverse-engineer code to find the flaw. They asked the AI to reveal it.
Don't miss
The eight-month timeline between Varonis's report in December 2025 and the patch in August 2026 is worth noting against the backdrop of this brief's other AI prompt injection tracking. Researcher Håkon Maloy reported a separate M365 Copilot memory poisoning issue in March 2026 with a mitigated-globally status as of June 22, 2026. Johann Rehberger reported memory writes and deletions through indirect prompt injection in Microsoft 365 Copilot separately. M365 Copilot's unauthenticated prompt injection path, tracked in Issue 98 as unpatched at the time, has now exceeded 160 days without a formal CVE or a complete patch confirmation. CoSnitch's consumer scope and eight-month patch timeline reflect the same dynamic visible in enterprise Copilot: the AI assistant attack surface is being disclosed faster than it is being closed. Copilot Personal users with Gmail, Google Drive, or Google Calendar connected through OAuth should review and audit those connections, remove integrations that are not actively used, and treat the Copilot memory feature as a potential persistence mechanism that warrants periodic review of its stored contents.
Potential actions
- Review and audit all OAuth integrations connected to Copilot Personal for any user whose account may have received a suspicious or unexpected Copilot link. Navigate to the Copilot Personal settings and review connected apps. Disconnect any integration that is not actively required. Gmail, Google Drive, and Google Calendar connections are the specific OAuth scopes documented in the CoSnitch exfiltration path.
- Review the contents of Copilot Personal's persistent memory feature for any unexpected or attacker-introduced entries. CoSnitch demonstrated the ability to perform memory poisoning as part of the attack chain. Memories stored in Copilot influence future responses and can persist across sessions. Access Copilot memory settings and review all stored items, removing any that are unfamiliar or unexpectedly specific about sensitive topics.
- For enterprise security teams, assess whether monitoring tools can detect anomalous data access originating from AI assistant sessions. The Varonis disclosure confirms that CoSnitch's exfiltration produces no log artifacts distinguishable from normal Copilot behavior. If monitoring coverage does not include the AI assistant access layer, the same detection gap applies to any future prompt injection attack through similar assistants.
The Sip
One link. Copilot fires an attacker prompt automatically. The prompt reads Gmail, Drive, Calendar, and memory. The data leaves through what looks like a normal Copilot URL fetch. No alert fires. The assistant did exactly what it was designed to do. The patch shipped eight months after the report. Review the OAuth connections and clear the memory.