Google Fixes GeminiJack Zero-Click Flaw in Gemini Enterprise

How the GeminiJack Attack Chain Worked
Noma Security detailed several stages in the GeminiJack attack sequence, showing how minimal attacker effort could trigger high-impact consequences:- Content Poisoning: An attacker creates a harmless-looking Google Doc, Calendar entry, or Gmail message. Hidden inside was a directive instructing Gemini Enterprise to locate sensitive terms within authorized Workspace data and embed those results into an image URL controlled by the attacker.
- Trigger: A regular employee performing a routine search could inadvertently cause the AI to fetch and process the tampered content.
- AI Execution: Once retrieved, Gemini misinterpreted the hidden instructions as legitimate. The system then scanned corporate Workspace data, based on its existing access permissions, for the specified sensitive information.
- Exfiltration: During its response, the AI inserted a malicious image tag. When the browser rendered that tag, it automatically transmitted the extracted data to the attacker's server using an ordinary HTTP request. This occurred without detection, sidestepping conventional defenses.