Skip to content
TechToolsHQ
NewsReviewsGuidesTech 101Tech SeriesToolsNewsletter
TechToolsHQ

Independent, research-driven tech coverage — breaking news, in-depth reviews, buying guides, and technical tutorials to help you understand and choose with confidence.

Explore
NewsReviewsGuidesTech 101Tech SeriesFree Tools
Legal
About UsOur AuthorsContact UsPrivacy PolicyTerms of ServiceCopyright & DMCAAffiliate DisclosureEditorial PolicyAdvertise With Us

© 2026 TechToolsHQ. All rights reserved.

News/Security/One click could make Microsoft Copilot leak your Gmail, Drive and Calendar
Security

One click could make Microsoft Copilot leak your Gmail, Drive and Calendar

Researchers chained three flaws in Copilot Personal into a single-click data theft — and found them by getting Copilot to explain its own defences. Microsoft patched on 18 August.

By Himanshu Bhatt· 4 min read· August 21, 2026

A paper cut-out of a human head labelled “AI”, filled with watching eyes.
Key Takeaways · TL;DR
  • Three flaws in Microsoft Copilot Personal, named CoSnitch and tracked as CVE-2026-24301.
  • One click on a normal-looking link was enough — no download, no credentials, no further interaction.
  • Reachable data included Gmail message bodies, Drive file names, Calendar entries, and Copilot's own chat history and memory.
  • Microsoft shipped patches on 18 August 2026; researchers found no evidence of exploitation in the wild.
  • The researchers found the final piece by asking Copilot to explain why the attack wouldn't work — and it told them.
☰ On this page(show)(close)
  • 1.What the attack could reach
  • 2.Copilot explained how to defeat it
  • 3.Nine months from report to patch
On this page
  • 1.What the attack could reach
  • 2.Copilot explained how to defeat it
  • 3.Nine months from report to patch

Researchers at Varonis Threat Labs chained three flaws in Microsoft Copilot Personal into an attack that needed nothing from the victim but one click on a legitimate-looking link — after which the assistant could be made to read the person's connected Gmail, Google Drive and Calendar and send what it found to an external server. Microsoft shipped patches on 18 August 2026, and the researchers say they found no evidence the attack was ever used in the wild.

INFO

What you need to do Nothing, if you are up to date. The fix shipped on 18 August 2026 and the flaws were never observed being exploited. This is worth reading for what it says about connecting AI assistants to your accounts, not because you are at immediate risk.

What the attack could reach

The three flaws — automatic prompt execution, data exfiltration to an external server, and persistent memory poisoning via web summarisation — were collectively named CoSnitch and are tracked as CVE-2026-24301. Chained, they gave an attacker reach into everything the victim's Copilot session could see: full email bodies, subject lines and sender and recipient metadata from connected mail; file names and metadata from Google Drive; calendar titles, attendees, times and locations; the full text of prior Copilot conversations; and the assistant's persistent memory — the saved instructions and rules that carry across sessions.

That list is the point, and it is not really about Microsoft. An AI assistant is useful in proportion to what you connect it to, and every connection widens what a single compromise reaches. A flaw in a note-taking app leaks notes. A flaw in an assistant wired to your mail, files and calendar leaks all three at once, through one interface, in a session you already authorised.

Copilot explained how to defeat it

The most striking part of the disclosure is how the last piece was found. The researchers pressed Copilot on why their attack should not work — and, in the course of refusing, it told them. Varonis writes: "Copilot then disclosed an undocumented URL parameter — unprompted, mid-refusal — including its historical behavior and every protection put in place to disable it." They call the technique meta-hacking: social-engineering the model's reasoning rather than attacking its code. Their summary is the sharpest line in the whole writeup: "Copilot wasn't breached; it was played."

It is worth sitting with that for a moment. The system was not tricked by a clever payload. It was asked to justify its own security, and the justification contained the answer. A model trained to be helpful and to explain itself will, under pressure, explain itself — including the parts that were meant to be undocumented.

Nine months from report to patch

Varonis reported the issue to Microsoft in December 2025. The patches arrived on 18 August 2026 — about eight months later. Neither source characterises that delay, so neither will we; complex fixes in a live AI product are not the same as a one-line web patch. What can be said plainly is that the window existed, and that the researchers found no sign anyone used it.

INFO

What a VPN would have done here: nothing Worth stating because the reflex is common. A VPN would not have prevented any part of this. The data left through an authorised session in an application you were signed into; encryption in transit was never the weak point. A VPN protects the pipe, not what the thing at the end of it has been persuaded to do. Our explainer on what a VPN does not protect you from covers exactly this gap, and this is a clean example of it.

CoSnitch is fixed, was never exploited, and in that narrow sense is a non-event. The reason it is worth your attention is the shape of it. The exploit did not defeat the model's defences so much as ask them politely to describe themselves — and the more capable and more connected these assistants become, the more a single click is worth to whoever is on the other end of it. That is not a bug that gets patched once.

Frequently asked questions

Was my data taken?
There is no evidence anyone used this. Varonis states it saw no exploitation in the wild, and The Hacker News reports the same. The research shows what was possible, not what happened.
Do I need to do anything?
Make sure Copilot is up to date. The fix shipped on 18 August 2026.
What could an attacker actually see?
Email bodies and metadata, Drive file names, calendar entries, prior Copilot conversations, and Copilot's saved memory — anything that session could reach.
Would a VPN or antivirus have stopped it?
No. The data moved through a session you had already authorised. Neither tool addresses that.
What is "memory poisoning"?
One of the three flaws let an attacker write instructions into Copilot's persistent memory via web summarisation — so the effect could outlast the original session rather than ending with it.
Should I disconnect my accounts from AI assistants?
That is a judgement about how much the convenience is worth. The useful lesson is narrower: each connection you add is another thing a single flaw in the assistant can reach, so connect what you actually use and not more.
Keep going

Where to go next

Tech 101

What is end-to-end encryption?

Why "encrypted" and "private" are not the same promise.

Read
News

OpenAI cuts GPT-5.6 Luna API prices by 80%

Our other coverage of where the AI tooling market is going.

Read

Drafted with AI assistance, verified against the cited study and primary sources, and edited by TechToolsHQ staff.

Share
Continue Reading

Related Stories & Next Reads

Close-up of the Windows key on a black laptop keyboard.
Security

Microsoft patched a Windows zero-day North Korean attackers were already using

Himanshu Bhatt · 4 min read · Aug 24, 2026
Chart showing 281 free Android VPNs audited: 61 plaintext, 29 leaks, 246 trackers, 76 ad-ID tracking
Security

Researchers audited 281 free Android VPNs: most track you, dozens leak your data

Himanshu Bhatt · 5 min read · Aug 24, 2026
A terminal screen reading “DATA TRANSFER COMPLETE — CONNECTION CLOSED” above a backlit keyboard.
Security

737 fake Chrome VPN extensions routed browser traffic through proxies

Himanshu Bhatt · 4 min read · Aug 22, 2026

Don't miss the next deep-dive

Weekly breakdowns of the tools students and builders actually use.

No spam·Unsubscribe any time·Privacy-first