CVE-2026-18236

CRITICALPre-NVD 9.39.3
EchelonGraph scoreLOW confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
Trending — 3 sources updated this week
9.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 9.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.3
EG Score
9.3(low)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

July 29, 2026

Last Modified

July 29, 2026

Advisory Details (1)

Auto-updated Jul 29, 2026
Patch available. Sources: github_commit.
github_commit Patch Available

commit c03f333769fe (google/adk-python)

Patch available: google/adk-python v2.5.0 (contains commit c03f333769fe)

https://github.com/google/adk-python/commit/c03f333769feaeaa9fe8910fbe95cb9f2d513f54

Vendor Advisories for CVE-2026-18236(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-30 08:17 UTCGHSA enrichment
  2. 2026-07-30 04:02 UTCGHSA enrichment
  3. 2026-07-29 23:48 UTCGHSA enrichment
  4. 2026-07-29 19:32 UTCGHSA enrichment
  5. 2026-07-29 18:30 UTCEG score recompute
  6. 2026-07-29 18:02 UTCEG score recompute
  7. 2026-07-29 18:02 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-18236?
CVE-2026-18236 is a critical vulnerability published on July 29, 2026. 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…
When was CVE-2026-18236 disclosed?
CVE-2026-18236 was first published in the National Vulnerability Database on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-18236?
CVE-2026-18236 has a CVSS v3 base score of 9.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-18236?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18236, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-18236

Explore →

Is Your Infrastructure Affected by CVE-2026-18236?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs