Skip to main content
CVE-2026-115522VulnerabilityPublished

FileArtifactService · Resource Exposure

Affects google-adk-pythonSource GCVE Database

0
Authoritative record:CVE-2026-115522· Medium 5.3

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, 07:28 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 google-adk-python to 2.7.0 or 1.39.1.

Affected software

ProductAffectedFixed in
PyPIgoogle-adk-pythonpkg:pypi/google-adk-pythonOther threatsAffected
  • <1.39.1
  • <2.7.0
Fixed in
  • 1.39.1
  • 2.7.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade affected Google ADK for Python versions to 1.39.1 or later in the 1.x series, or 2.7.0 or later in the 2.x series. These versions remove the legacy fallback path and enforce full per-application path scoping, preventing cross-application artifact access. No other mitigation is indicated by the vendor advisory.

Description

A vulnerability in Google Agent Development Kit (ADK) for Python's FileArtifactService allows an application to access artifacts of another application when both share a root directory and user ID. This occurs because the service accepted an application name in its API but did not use it when constructing on-disk paths, leading to cross-application access. The issue affects versions before 1.39.1 in the 1.x series and before 2.7.0 in the 2.x series. The vulnerability was addressed by enforcing full per-application path scoping in version 2.7.0 and backported to 1.39.1. The CVSS 4.0 base score is 5.3, indicating medium severity.

References

Community reviews

Loading reviews…