Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

Google Cloud Platform (GCP) Dialogflow Service Agent Token Leak and Abuse Through Conversational Agents

Low

Synopsis

Tenable Research has identified and responsibly disclosed a critical privilege escalation vulnerability in Google Dialogflow. This flaw allowed an attacker with access to a Dialogflow agent to take over the Dialogflow service agent and assume its privileged permissions.

 

This vulnerability stems from a misconfiguration in how Dialogflow's conversational agents handle authentication for their internal tools. When a user interacts with a predefined or custom agent, certain tools (such as the BigQuery tool) are executed using the Dialogflow service agent's identity. This service agent is provisioned with a broad set of permissions across various Google Cloud services.

 

An attacker could exploit this by configuring an agent to use a tool with an ID token authentication method and a Google API URL. When the victim interacts with the agent and triggers the tool, the service agent's ID token is used to authenticate to the API. This vulnerability allows users with the dialogflow.tools.update permission to invoke Cloud Functions and Cloud Run without explicit IAM permissions for Cloud Functions or Cloud Run invocation.

 

Proof of Concept

  1. Access Diagflow CX
  2. Create the predefined Movies agent
  3. Go to Tools --> bq tool
  4. Change the authentication method to ID token with a service agent

Authentication dialog with Service agent token and ID token selected

  1. Change the URL to an external API

schema view showing where to change the server

  1. Communicate with the agent and trigger the tool
Preview
  1. API is called with the Service Agent permissions

Solution

Google has remediated the issue.

Disclosure Timeline

June 10, 2025 - Tenable reports the finding to Google and Google acknowledges
June 20, 2025 - Tenable asks for updates on the report
June 25, 2025 - Google asks questions on the exploitation and Tenable answers
June 26, 2025 - Google asks questions on the exploitation and Tenable answers
July 2, 2025 - Google asks for a POC
July 6, 2025 - Tenable provides a POC and an additional explanation
July 14, 2025 - Google assigns S1 severity
July 15, 2025 - Google asks for more details and Tenable clarifies and responds
July 25, 2025 - Google requests a correction of the disclosure date until 9/8/2025
July 27, 2025 - Tenable accepts Google's request for correction
July 28, 2025 - Google provides an update regarding the fix
July 31, 2025 - Tenable agreed to delay the disclosure date to 10/23/2025
August 11, 2025 - Google updates their product team has started working on a mitigation and it should be code complete in the next 30 days and then roll out into production
August 12, 2025 - Google awards a bounty
August 25, 2025 - Google updates that they are still working on the fix
September 5, 2025 - Google clarifies the impact of the vulnerability based on their testing
September 28, 2025 - Tenable asks for a status update
October 11, 2025 - Google marks the issue as fixed

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]

Risk Information

Tenable Advisory ID: TRA-2025-48
Credit:
Liv Matan
Affected Products:
GCP Dialogflow
Risk Factor:
Low

Advisory Timeline

October 23, 2025 - Initial release.
× Contact our sales team