CVE-2026-115522
Received Received - Intake

Exposure of Resource to Wrong Sphere in Google ADK for Python

Vulnerability report for CVE-2026-115522, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-28

Last updated on: 2026-10-28

Assigner: Google Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-28
Last Modified
2026-10-28
Generated
2026-10-28
AI Q&A
2026-10-28
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-668 The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an Exposure of Resource to Wrong Sphere (CWE-668) in Google Agent Development Kit (ADK) for Python. It allows a caller in one application to access artifacts belonging to another application when both share a FileArtifactService root directory and use the same user_id. The issue occurred because the service accepted app_name in APIs but stored artifacts under a shared path (root/users/{user_id}/...) instead of app-specific paths (root/apps/{app_name}/users/{user_id}/...). Versions 1.39.1 and 2.7.0 fixed this by enforcing app-scoped paths.

Detection Guidance

Check if your google-adk version is below 1.39.1 or 2.7.0. Inspect FileArtifactService paths for artifacts stored in root/users/{user_id} instead of root/apps/{app_name}/users/{user_id}. Verify if multiple apps share the same root directory and user_id, which could indicate potential cross-app access.

Impact Analysis

This vulnerability could allow unauthorized access to sensitive data across different applications. If two apps share a root directory and use the same user_id, one app could list, read, overwrite, or delete artifacts belonging to the other app. This includes session-scoped artifacts if session_id matches. The impact includes data leakage, corruption, or loss of critical files.

Compliance Impact

This vulnerability could violate data isolation requirements in GDPR and HIPAA. GDPR mandates strict data access controls and user consent for data sharing. HIPAA requires safeguards to prevent unauthorized access to protected health information. Cross-app data leakage could lead to non-compliance, legal penalties, and loss of trust.

Mitigation Strategies
  • Upgrade google-adk to version 1.39.1 or 2.7.0 or later to enforce app-scoped artifact storage.
  • Ensure each application uses a unique root directory to prevent shared access between apps.
  • Manually migrate existing artifacts from old paths (root/users/{user_id}) to new app-scoped paths (root/apps/{app_name}/users/{user_id}) if upgrading past version 2.6.0.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-115522. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart