Live › vulnerability › CVE-2026-107858
Go to dashboardThe ADK development web server in Google Agent Development Kit for Java accepts WebSocket and cross-origin requests from any website, with no authentication. A malicious page open in a developer's browser while the server runs can send messages to the agent, trigger its tools, and read or change its sessions and artifacts.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Developers running the ADK development web server (the dev-only server, not a production deployment) from the Java package versions listed. Exposure comes from a developer browsing a malicious page while the server is running; binding to localhost does not prevent it because requests come from the developer's own browser. Teams that do not run the dev web server, or that run only on versions 1.13.0 and later, can skip it.
No product ranges from the sources yet.
com.google.adk:google-adk-dev and com.google.adk:google-adk-maven-plugin and note the version.adk web or the dev server) was started on the machine, and whether adk.web.cors.origins is set in the configuration.com.google.adk:google-adk-dev and com.google.adk:google-adk-maven-plugin to 1.13.0 or later.1.6.0 through 1.12.0, set adk.web.cors.origins to an explicit allowlist such as http://localhost:8000.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-107858")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.