Technical impact
FileArtifactService in the Google Agent Development Kit for Python fails to enforce per‑application isolation when mapping artifact names to on‑disk paths. The service accepts an app_name parameter in its public API but does not incorporate it into the path construction; the resulting paths omit the app_name and use only root/users/{user_id}/, allowing artifacts for one application to be accessible under another application's context. This flaw permits a caller that has access to one application’s artifacts to enumerate, read, overwrite, or delete artifacts belonging to any other application that uses the same root directory and user_id (and session_id for session‑scoped artifacts).
Affected Systems
All installations of Google Agent Development Kit for Python versions 1.19.0 through 1.38.x as well as 1.39.0, and 2.0.0a1 through 2.6.x are affected. Upgrades to version 1.39.1 for 1.x releases or 2.7.0 for 2.x releases eliminate the fallback to root/users/{user_id} and enforce full per‑app path scoping.
Risk and Exploitability
Based on the description, the likely attack vector is a local or shared‑deployment scenario where an attacker has code execution or process access that shares the same FileArtifactService root directory and user identity. In such a scenario, the attacker can enumerate, read, overwrite, or delete artifacts belonging to other applications that reside under the same root. The CVSS score of 5.3 indicates moderate severity, while the EPSS score of <1% signals a very low probability of exploitation at the time of assessment. The vulnerability is not listed in the CISA KEV catalog. If exploited, the attacker can compromise confidentiality, integrity, and availability of artifacts belonging to other applications on the same host.