# CVE-2026-18236: Google-ADK Continuation Forgery

> Attackers can execute unauthorized tools by forging confirmation responses due to missing validation of tool registration and arguments in Google ADK.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-8qg5-x5vm-75jx

## What is CVE-2026-18236?

CVE-2026-18236 is a critical missing authorization vulnerability in Google-ADK, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the Agent Development Kit (ADK) allows for continuation forgery in tool confirmations. An attacker who is able to manipulate or inject events into the session history can execute unauthorized tools by forging a tool confirmation response. This is possible because the framework did not verify if the target tool was registered to the executing agent, did not validate if the tool actually required confirmation, and did not match the confirmation arguments against the original tool call event in the history.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-18236?


## How do I fix CVE-2026-18236?

No fix has been published for CVE-2026-18236 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-18236 being exploited?

There is no known exploitation of CVE-2026-18236 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-18236 and fix it if it is affected.

What it is: CVE-2026-18236 is a critical missing authorization vulnerability in Google-ADK, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18236 in the wild and no public exploit code.

Affected product: Google-ADK. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-18236/ (Markdown: https://insights.sbomify.com/CVE-2026-18236/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-18236
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-18236
- OSV: https://osv.dev/vulnerability/CVE-2026-18236

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-18236/
Summaries are generated and may contain mistakes; the official description above is the record.