CVE-2026-115522: Google Agent Development Kit (ADK) for Python · Resource Exposure
Affects Google Agent Development Kit (ADK) for PythonSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.7.0 or 1.39.1 when convenient.
Data as of 28 Oct 2026, 04:57 UTC
- Patch
- Available – fixed in 2.7.0, 1.39.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Agent Development Kit (ADK) for Python and google-adk to 2.7.0 or 1.39.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Agent Development Kit (ADK) for Pythongoogle-adk | Affected
| Fixed in
|
| Agent Development Kit (ADK) for Pythongoogle-adk | Affected
| Fixed in
|
GitHubgoogle-adkpkg:github/google-adkOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in Google ADK for Python versions 1.39.1 and 2.7.0, which enforce full per-application path scoping. Users should upgrade to these versions or later to remediate the issue. No additional mitigations are indicated by the vendor advisory.
Description
CVE-2026-115522 is a vulnerability in Google Agent Development Kit (ADK) for Python that allows an application to access or modify artifacts belonging to another application when both share a FileArtifactService root directory and the same user_id. This occurs because the service omitted the application name when constructing on-disk paths, leading to improper resource isolation. The issue affects versions 1.19.0 through before 1.39.1 and 2.0.0a1 through before 2.7.0. The vulnerability was fixed by enforcing full per-application path scoping in versions 1.39.1 and 2.7.0.
References
- github.com/google/adk-python/issues/5618 (opens in a new tab)
- github.com/google/adk-python/pull/5619 (opens in a new tab)
- github.com/google/adk-python/commit/f72f0db58c5c1f4e8b8d4f04b8c592c9e49cbe9e (opens in a new tab)
- github.com/google/adk-python/commit/c27d8688ed9ea619587ad96cbfd641c34dd7340c (opens in a new tab)
- github.com/google/adk-python/commit/0ae2bffdd2628af6c8643bc4fd40c2f49f0c6bd4 (opens in a new tab)
- github.com/google/adk-python/releases/tag/v1.39.1 (opens in a new tab)
- github.com/google/adk-python/releases/tag/v2.7.0 (opens in a new tab)