Remote Code Execution in Google Agent Development Kit (ADK)
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.28.1, 2.0.0a2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 Nuclei template
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
A Code Injection and Missing Authentication vulnerability in Google Agent Development Kit (ADK) versions 1.7.0 (and 2.0.0a1) through 1.28.1 (and 2.0.0a2) on Python (OSS), Cloud Run, and GKE allows an unauthenticated remote attacker to execute arbitrary code on the server hosting the ADK instance. This vulnerability was patched in versions 1.28.1 and 2.0.0a2. Customers need to redeploy the upgraded ADK to their production environments. In addition, if they are running ADK Web locally, they also need to upgrade their local instance.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Google Cloud Agent Development Kit (ADK)
From 1.7.0 · fixed in 1.28.1; From 2.0.0a1 · fixed in 2.0.0a2
- google-adkPyPI
From 1.7.0 · fixed in 1.28.1; From 2.0.0a1 · fixed in 2.0.0a2
- google-adkPyPI
From 1.7.0 · fixed in 1.28.1
- google-adkPyPI
From 2.0.0a1 · fixed in 2.0.0a2