CVE-2026-4810
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA critical code injection and missing authentication vulnerability in Google Agent Development Kit (ADK) versions 1.7.0 through 1.28.1 (and 2.0.0a1 through 2.0.0a2) on Python (OSS), Cloud Run, and GKE allows unauthenticated remote attackers to execute arbitrary code on servers hosting ADK instances.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Amber
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed ADK versionRun `pip show google-adk` or `pip list | grep google-adk` to see the installed package versionAffected if Version is 1.7.0 through 1.28.1 or 2.0.0a1 through 2.0.0a2 (inclusive)
-
Confirm ADK deployment platformCheck whether the ADK is deployed on Python (standalone/OSS), Google Cloud Run, or Google GKE based on your infrastructure configurationAffected if Deployment uses Python (OSS), Cloud Run, or GKE platform
-
Verify network exposure of ADK serviceExamine the ADK web service configuration to determine if it is exposed to network access (check service binding, firewall rules, or ingress settings)Affected if The ADK service is network-accessible from untrusted sources or the internet
You are affected if the installed ADK version is between 1.7.0 and 1.28.1 (inclusive) or between 2.0.0a1 and 2.0.0a2 (inclusive) AND it is deployed on Python (OSS), Cloud Run, or GKE with network accessibility.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade ADK to versions 1.28.1 or 2.0.0a2 and redeploy to production environments. Local ADK Web instances must also be upgraded.
1.28.1 (stable) or 2.0.0a2 (alpha)
- Upgrade the Google ADK Python package to version 1.28.1 or later by running: pip install google-adk>=1.28.1
- If using Cloud Run, rebuild and redeploy your ADK container image using the updated package version
- If using GKE, rebuild your container images and redeploy the pods to the updated ADK version
- If running ADK Web locally, upgrade your local ADK installation to version 1.28.1 or later
- After redeployment, verify the service is running and accessible, and confirm authentication is now properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4810 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data