CVE-2026-79696

10.0

Google · Agent Development Kit (ADK) for Python

An unauthenticated remote code injection vulnerability exists in Google Cloud Agent Development Kit for Python, allowing arbitrary code execution via crafted test session replays.

Executive summary

A critical code injection vulnerability in Google Cloud Agent Development Kit for Python allows unauthenticated remote attackers to execute arbitrary code, posing a severe risk to system integrity.

Vulnerability

This is a code injection vulnerability stemming from incomplete input validation (CWE-184) within the adk web component. An unauthenticated remote attacker can trigger this flaw by sending a crafted test session replay, which is then processed by the underlying pytest environment.

Business impact

The potential for unauthenticated remote code execution grants an attacker full control over the affected environment, including Cloud Run and GKE instances. Given the CVSS score of 10.0, this represents a critical threat that could lead to complete data exfiltration, unauthorized system modification, and significant operational disruption.

Remediation

Immediate Action: Upgrade the Google Cloud Agent Development Kit for Python to version 2.7.0 or later immediately to resolve the vulnerable code path.

Proactive Monitoring: Review access logs for unusual traffic patterns targeting the adk web component and monitor for unexpected child processes spawned by the Python environment.

Compensating Controls: Ensure that the adk web interface is not exposed to the public network, and utilize network access control lists to restrict traffic to trusted sources only.

Exploitation status

Public Exploit Available: Unknown.

Analyst recommendation

This vulnerability presents an extreme risk due to the lack of required authentication and the potential for total system compromise. Organizations running the affected versions of the Google Cloud Agent Development Kit for Python must prioritize updating to version 2.7.0. If an immediate update is not feasible, ensure the service is isolated from all untrusted network access to prevent remote exploitation.

More Google CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief critical section

Sources

Originally found and disclosed by Sanil Dulal, per the CVE Program record.