Level 1. Deviation
Google Dialogflow CX Bug Allowed Attackers to Hijack AI Conversations
- Developer
- Not established
- Model
- Not established
- When it happened
- July 7, 2026
- When it was disclosed
- Not established
- How well it is stood up
- Not verified yet
- What caused it
- Not established
- Where it stands now
- Not established
What happened
Reported by securityweek.com. Listed here with a link to their report. Nobody on this side has checked it against that report, so it carries no level and this is not our account of what happened.
Our assessment
- Actual
- 1 of 5Deviation
- Potential
- 3 of 5Significant control incident
The system behaved contrary to its instructions, and it stayed contained. The potential level is what the behaviour demonstrated here could credibly have led to, judged from the same evidence.
This level rests on news reports. The developer has not confirmed it here.
This happened in a test, an evaluation or a demonstration. Nobody real was harmed, so the actual level stays at 1. What it showed counts toward the potential level.
Google patched it; Varonis found no in-the-wild abuse.
Why this level
- Sensitive data was reachable. Argues for a potential level of 3
- A security boundary was crossed. Argues for a potential level of 3
- Significant data was exposed. Argues for a potential level of 3
What is established, and what is not
Confirmed
Nothing is confirmed yet.
Reported, not confirmed
A security boundary was crossed. A claim, so it counts toward potential only
The cybersecurity firm also discovered that it could establish a bidirectional communication channel to an external server, bypassing VPC Service Controls (used to enforce data perimeters), and that the Instance Metadata Service (IMDS) within the Cloud Run environment could be targeted to retrieve access tokens for a Google-managed service account.
Google Dialogflow CX Bug Allowed Attackers to Hijack AI ConversationsSensitive data was reachable. A claim, so it counts toward potential only
Dialogflow CX is an enterprise-grade conversational AI platform that allows organizations to build complex virtual agents and chatbots for customer support, financial services, healthcare assistance, and sensitive data-handling workflows within enterprise environments.
Google Dialogflow CX Bug Allowed Attackers to Hijack AI ConversationsSignificant data was exposed. A claim, so it counts toward potential only
Attackers could silently take control of every agent in the same GCP project, manipulate conversations, and exfiltrate sensitive data without detection.
Google Dialogflow CX Bug Allowed Attackers to Hijack AI Conversations
Checked, and did not happen
Nothing here was checked and ruled out.
Not confirmed
Nothing is outstanding.
Where this came from
The original report · read September 20, 2026
Google Dialogflow CX Bug Allowed Attackers to Hijack AI ConversationsA structured incident database · read September 18, 2026
AI Failure Index (CC-BY-4.0 data fields)Where we first saw it
A 'Rogue Agent' flaw in Google Dialogflow CX let one permission hijack every chatbot in a projectWhere we first saw it
Exclusive: Google patched AI chatbot flaw that could have exposed customer conversations
The reports above are other people’s. The levels are ours, worked out under our published rules. No organisation that reported this assigned our number, and none of it is legal advice.
Something here is wrong? Tell us. Send us a source we can open, and a person will read it.