A recently disclosed vulnerability in Google’s Agent Development Kit (ADK) serves as a stark reminder that even the most modular frameworks are not immune to classic security pitfalls.
Security researchers have identified a critical flaw, tracked as CVE-2026-4810, which carries a CVSS score of 9.3. The vulnerability combines Code Injection with Missing Authentication, effectively leaving the door wide open for unauthenticated remote attackers to take control of the servers hosting these AI agents.
At its core, the Google ADK is designed to be a flexible, modular framework that simplifies the creation, deployment, and orchestration of agent workflows. While it is optimized for Gemini, its “model-agnostic” and “deployment-agnostic” nature means it is widely used across Python (OSS), Cloud Run, and Google Kubernetes Engine (GKE) environments.
The danger of CVE-2026-4810 lies in its unauthenticated nature. Because the framework was found to have missing authentication checks in certain configurations, a remote attacker can bypass standard security gates. When paired with the code injection flaw, this allows for Remote Code Execution (RCE). In plain terms, an attacker can send malicious commands to the server and have them executed with the same privileges as the ADK instance itself.
The vulnerability impacts a significant range of versions across several common deployment platforms. Organizations utilizing ADK for Python-based open-source projects or those running agents on Google’s managed cloud services are at the highest risk.
| Deployment Platform | Affected Versions |
| Python (OSS) | 1.7.0 (and 2.0.0a1) through 1.28.1 (and 2.0.0a2) |
| Cloud Run | 1.7.0 (and 2.0.0a1) through 1.28.1 (and 2.0.0a2) |
| GKE | 1.7.0 (and 2.0.0a1) through 1.28.1 (and 2.0.0a2) |
Google has moved quickly to address the flaw, releasing patches in versions 1.28.1 and 2.0.0a2. However, for this specific fix, a simple package update may not be enough to fully secure your environment.
Administrators and developers are urged to redeploy their upgraded ADK instances to their production environments immediately. Furthermore, if your team utilizes ADK Web for local development or testing, those local instances must also be updated to prevent lateral movement or local compromise.
Support Our Threat Intelligence
If you find our CVE report and cybersecurity news helpful, consider supporting our work.