CVE Intelligence
Analysis AI-assisted

CVE-2026-4810: Google ADK Code Injection and Missing Authentication

CVE-2026-4810 affects Google Agent Development Kit (ADK) on Python (OSS), Cloud Run and GKE, and combines code injection with missing authentication according to the record. The CNA rates it critical with a CVSS v4.0 score of 9.3, and the record states that an unauthenticated remote attacker could execute code on the host. The issue is reported as fixed in versions 1.28.1 and 2.0.0a2, and no confirmed exploitation appears in the sources consulted.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

CVE-2026-4810 is a critical flaw in Google Agent Development Kit (ADK). The record describes it as a combination of code injection and missing authentication, classified under CWE-306 (Missing Authentication for Critical Function). According to the record, the issue was patched in versions 1.28.1 and 2.0.0a2.

Impact

  • An unauthenticated remote attacker could, as described, execute arbitrary code on the server hosting an ADK instance.
  • The CNA-provided CVSS v4.0 base score is 9.3 (critical), and the vector in the record marks confidentiality, integrity and availability impact as high for the vulnerable system.
  • Because the description covers Python (OSS), Cloud Run and GKE deployments, any of these hosting models may be relevant to a review.

Affected products and versions

  • Product: Google Agent Development Kit (ADK), as stated in the record.
  • Platforms named: Python (OSS), Cloud Run and GKE.
  • Range as written in the record: versions 1.7.0 (and 2.0.0a1) through 1.28.1 (and 2.0.0a2).
  • The structured affected and fixes fields in the record are empty, so the version information comes only from the narrative description. See the CVE Record.

Exploitation status

  • The record shows the vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog.
  • No confirmed exploitation appears in the sources consulted for this analysis.
  • The EPSS probability is 0.02211 with a percentile of 0.82149 as recorded. This is a statistical estimate and not evidence of exploitation.

Remediation and mitigation

  • Upgrade ADK to version 1.28.1 or to version 2.0.0a2, depending on the release line in use.
  • Redeploy the upgraded ADK to production environments, including Cloud Run and GKE workloads, since the record states redeployment is required.
  • Upgrade local instances of ADK Web as well.
  • Until upgrades are complete, reduce network exposure of ADK instances and review which endpoints are reachable without authentication.
  • Confirm the fix by checking the running version after redeployment, not only the build artifact.

Detection guidance

  • Inventory all ADK installations, container images, Cloud Run revisions and GKE workloads, and record their versions.
  • Review logs for unexpected requests to ADK endpoints and for unexpected process or file activity on hosts running ADK.
  • Check for unexpected configuration or agent changes that were not made by authorized teams.
  • Treat detection as a supplement to patching, since the record does not describe specific indicators of compromise.

Limitations of the available information

  • The record has no title, no structured affected or fixed version data, and no exploit details beyond the narrative description.
  • The record's range notation for the alpha track is kept as written; the exact set of builds between the stated boundaries is unknown.
  • The changelog link in the record uses an anchor whose text was not verified against the 1.28.1 entry; check the changelog directly.
  • The EPSS date in the record is later than the publication date and should be verified against the source before relying on it.
  • No independent vendor advisory text was reviewed beyond the record.

Frequently asked questions

Is CVE-2026-4810 being actively exploited?

The record shows it is not listed in CISA KEV, and no confirmed exploitation appears in the sources consulted. This does not rule out future exploitation, so patching remains the priority.

Which versions contain the fix?

The record states the vulnerability was patched in versions 1.28.1 and 2.0.0a2. Check the official changelog to confirm the release details for your line.

Do local ADK Web installations need updating?

Yes. The record states that customers running ADK Web locally also need to upgrade their local instance.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.