---
id: "CVE-2026-107858"
kind: "vulnerability"
aliases: ["CVE-2026-107858"]
title: "Google ADK dev web server: any website can control local agents"
severity: "high"
cvss: 7.2
epss: 0.0036
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-agents", "ai-tooling", "developer-machines", "google-adk", "java"]
not_affected_if: ["dev-server-not-running", "production-only", "version-1.13.0-or-later"]
published_at: "2026-10-23T06:17:03+00:00"
first_seen_at: "2026-10-23T21:57:32+00:00"
updated_at: "2026-10-25T03:27:46+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-107858", "first_seen_at": "2026-10-23T21:57:32+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-107858", "first_seen_at": "2026-10-24T07:15:51+00:00"}]
---

# Google ADK dev web server: any website can control local agents

The 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, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Maven dependency for `com.google.adk:google-adk-dev` and `com.google.adk:google-adk-maven-plugin` and note the version.
- Confirm whether the ADK web server (`adk web` or the dev server) was started on the machine, and whether `adk.web.cors.origins` is set in the configuration.

## Fix

- Upgrade `com.google.adk:google-adk-dev` and `com.google.adk:google-adk-maven-plugin` to `1.13.0` or later.
- On versions `1.6.0` through `1.12.0`, set `adk.web.cors.origins` to an explicit allowlist such as `http://localhost:8000`.

## Timeline

- 2026-10-23T21:57:32+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-107858
- 2026-10-24T07:15:51+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-107858

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_