Google Gemini Indirect Prompt Injection via Calendar Invites Leaks Private Schedule Data
Researchers reported an indirect prompt-injection issue in Google Gemini’s integration with Google Calendar that allows a malicious calendar invite to act as a dormant instruction payload. By crafting natural-language directives in an event’s description field, an attacker can cause Gemini—when later asked routine questions like “What’s my schedule today?”—to ingest the attacker-controlled event content and follow embedded instructions that result in exfiltration of private calendar details (e.g., summarizing private meetings) into attacker-visible locations such as a newly created calendar event description.
Both reports attribute the finding to Miggo Security, describing how the attack can bypass expected privacy controls by exploiting Gemini’s helpful behavior of parsing and acting on calendar data. The technique does not require traditional code execution; it relies on Gemini interpreting attacker-supplied text as instructions, enabling outcomes such as leaking sensitive meeting information and creating deceptive events. This highlights a broader risk pattern for LLM assistants embedded in productivity suites: attacker-controlled content in first-party data fields (like invites) can be weaponized to manipulate the assistant’s actions and data handling.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
5 events from the most recent confirmed update back to the earliest known activity.
Researchers publicly disclose the Gemini Calendar attack technique
On January 20, 2026, multiple reports described Miggo's public disclosure of the flaw, including the attack chain, its bypass of Google's prompt defenses, and the risk of exposing private meeting details through malicious calendar invites.
Google adds mitigations and fixes the reported Gemini flaw
Google implemented mitigations for the specific exploit and later confirmed the vulnerability had been fixed, addressing the reported exposure of private Google Calendar meeting data through Gemini.
Miggo reports Gemini Calendar data-exfiltration issue to Google
After validating the attack, Miggo shared its findings with Google, describing how Gemini could be induced to summarize private meetings and write the stolen details into a newly created calendar event.
Miggo discovers Calendar invite prompt-injection flaw in Gemini
Miggo Security identified an indirect prompt-injection vulnerability in Google Gemini's Google Calendar integration, where malicious natural-language instructions embedded in a calendar invite description could remain dormant until a user asked Gemini about their schedule.
SafeBreach demonstrates earlier Calendar/Gemini prompt-injection technique
An August 2025 SafeBreach demonstration showed prior prompt-injection risks involving Google Calendar and Gemini, establishing earlier research into abusing calendar content to influence the assistant.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
5 references tracked. Mallory keeps watching after this page renders.
Calendar Spy: How "Indirect Prompt Injection" Turned Google Gemini Into a Spy
securityonline.info
Open sourceMalicious Google Calendar invites could expose private data | Malwarebytes
malwarebytes.com
Open sourceGoogle Gemini flaw allowed meeting data exposure | SC Media
scworld.com
Open sourceGemini AI assistant tricked into leaking Google Calendar data
bleepingcomputer.com
Open sourceGoogle Gemini Flaw Turns Calendar Invites Into Attack Vector
darkreading.com
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


