CVE Catalog

CVE-2026-107858

HighCVSS 7.2
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.36%

30th percentile - higher than 30% of all known CVEs

Summary

The development web server (ADK Web) in Google Agent Development Kit (ADK) for Java lacks WebSocket origin validation and uses a permissive cross-domain policy. This allows a remote attacker to control a locally running agent and read its data via a malicious web page visited by a developer while the server is running. The issue is fixed in version 1.13.0.

Risk Assessment

A developer visiting a malicious page while the server runs may trigger agent tools, leak data, and list, read, create, or delete sessions and artifacts. Lack of authentication and localhost binding do not prevent exploitation.

Recommendation

Update ADK to version 1.13.0. In versions 1.6.0 through 1.12.0, set the adk.web.cors.origins property to an explicit allowlist of trusted origins.

Related vulnerabilities

Original NVD description (English source)

Missing Origin Validation in WebSockets (CWE-1385) and Permissive Cross-domain Policy with Untrusted Domains (CWE-942) in the development web server (ADK Web) in Google Agent Development Kit (ADK) for Java (com.google.adk:google-adk-dev versions 0.1.0 before 1.13.0 and com.google.adk:google-adk-maven-plugin versions 0.3.0 before 1.13.0) allow a remote attacker to control a locally running agent and read its data via a malicious web page visited by a developer while the server is running. The /run_live WebSocket endpoint accepts connections from any origin by default (hardcoded via setAllowedOrigins("*") in versions 0.1.0 through 1.5.0, and defaulting to * via adk.web.cors.origins in versions 1.6.0 through 1.12.0), and since version 0.4.0 the REST API returns Access-Control-Allow-Origin: * by default. Because the server has no authentication and requests originate from the developer's browser (so binding to localhost does not prevent exploitation), a cross-origin page can send messages to the agent (triggering registered tools), stream agent responses, and list, read, create, or delete sessions and artifacts. In versions 1.6.0 through 1.12.0, users can mitigate the issue by setting the adk.web.cors.origins property to an explicit allowlist of trusted origins (such as http://localhost:8000). The vulnerability is fixed in version 1.13.0, which enforces a same-origin default for CORS and the /run_live WebSocket endpoint, and rejects DNS-rebinding requests over loopback.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS