CVE-2026-115522 (GCVE-0-2026-115522)
Vulnerability from cvelistv5 – Published: 2026-10-28 04:36 – Updated: 2026-10-28 04:36
VLAI
EPSS
VEX
Title
Cross-Application Artifact Namespace Isolation in Google Agent Development Kit (ADK) for Python
Summary
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.
Severity
CWE
- CWE-668 - Exposure of Resource to Wrong Sphere
Assigner
References
7 references
| URL | Tags |
|---|---|
| https://github.com/google/adk-python/issues/5618 | issue-trackingexploit |
| https://github.com/google/adk-python/pull/5619 | patch |
| https://github.com/google/adk-python/commit/f72f0… | patch |
| https://github.com/google/adk-python/commit/c27d8… | patch |
| https://github.com/google/adk-python/commit/0ae2b… | patch |
| https://github.com/google/adk-python/releases/tag… | release-notes |
| https://github.com/google/adk-python/releases/tag… | release-notes |
Impacted products
1 product
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| Agent Development Kit (ADK) for Python |
Affected:
1.19.0 , < 1.39.1
(semver)
Affected: 2.0.0a1 , < 2.7.0 (semver) |
guessed |
Date Public
2026-07-29 00:00
{
"containers": {
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"packageName": "google-adk",
"product": "Agent Development Kit (ADK) for Python",
"repo": "https://github.com/google/adk-python",
"vendor": "Google",
"versions": [
{
"lessThan": "1.39.1",
"status": "affected",
"version": "1.19.0",
"versionType": "semver"
},
{
"lessThan": "2.7.0",
"status": "affected",
"version": "2.0.0a1",
"versionType": "semver"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "@Nant361"
}
],
"datePublic": "2026-07-29T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eExposure of Resource to Wrong Sphere (CWE-668) in \u003ccode\u003eFileArtifactService\u003c/code\u003e in Google Agent Development Kit (ADK) for Python (\u003ccode\u003egoogle-adk\u003c/code\u003e) 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 \u003ccode\u003eFileArtifactService\u003c/code\u003e root directory and use the same \u003ccode\u003euser_id\u003c/code\u003e (and \u003ccode\u003esession_id\u003c/code\u003e for session-scoped artifacts). \u003ccode\u003eFileArtifactService\u003c/code\u003e accepted \u003ccode\u003eapp_name\u003c/code\u003e across its public API methods but omitted \u003ccode\u003eapp_name\u003c/code\u003e when constructing on-disk paths (\u003ccode\u003eroot/users/{user_id}/...\u003c/code\u003e instead of \u003ccode\u003eroot/apps/{app_name}/users/{user_id}/...\u003c/code\u003e). Version 2.6.0 scoped writes by \u003ccode\u003eapp_name\u003c/code\u003e but retained a legacy \u003ccode\u003eroot/users/{user_id}\u003c/code\u003e 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.\u003c/p\u003e"
}
],
"value": "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."
}
],
"impacts": [
{
"capecId": "CAPEC-1",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "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",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-668",
"description": "CWE-668 Exposure of Resource to Wrong Sphere",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-28T04:36:49.927Z",
"orgId": "14ed7db2-1595-443d-9d34-6215bf890778",
"shortName": "Google"
},
"references": [
{
"tags": [
"issue-tracking",
"exploit"
],
"url": "https://github.com/google/adk-python/issues/5618"
},
{
"tags": [
"patch"
],
"url": "https://github.com/google/adk-python/pull/5619"
},
{
"tags": [
"patch"
],
"url": "https://github.com/google/adk-python/commit/f72f0db58c5c1f4e8b8d4f04b8c592c9e49cbe9e"
},
{
"tags": [
"patch"
],
"url": "https://github.com/google/adk-python/commit/c27d8688ed9ea619587ad96cbfd641c34dd7340c"
},
{
"tags": [
"patch"
],
"url": "https://github.com/google/adk-python/commit/0ae2bffdd2628af6c8643bc4fd40c2f49f0c6bd4"
},
{
"tags": [
"release-notes"
],
"url": "https://github.com/google/adk-python/releases/tag/v1.39.1"
},
{
"tags": [
"release-notes"
],
"url": "https://github.com/google/adk-python/releases/tag/v2.7.0"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eUpgrade Google Agent Development Kit (ADK) for Python (\u003ccode\u003egoogle-adk\u003c/code\u003e) to version 1.39.1 (for 1.x installations) or version 2.7.0 (for 2.x installations) or later.\u003c/p\u003e"
}
],
"value": "Upgrade Google Agent Development Kit (ADK) for Python (google-adk) to version 1.39.1 (for 1.x installations) or version 2.7.0 (for 2.x installations) or later."
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "Cross-Application Artifact Namespace Isolation in Google Agent Development Kit (ADK) for Python",
"x_generator": {
"engine": "Vulnogram 1.0.2"
}
}
},
"cveMetadata": {
"assignerOrgId": "14ed7db2-1595-443d-9d34-6215bf890778",
"assignerShortName": "Google",
"cveId": "CVE-2026-115522",
"datePublished": "2026-10-28T04:36:49.927Z",
"dateReserved": "2026-10-22T18:18:29.284Z",
"dateUpdated": "2026-10-28T04:36:49.927Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-115522",
"date": "2026-10-28",
"epss": "0.00378",
"percentile": "0.3163"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"packageName": "google-adk",
"product": "Agent Development Kit (ADK) for Python",
"repo": "https://github.com/google/adk-python",
"vendor": "Google",
"versions": [
{
"lessThan": "1.39.1",
"status": "affected",
"version": "1.19.0",
"versionType": "semver"
},
{
"lessThan": "2.7.0",
"status": "affected",
"version": "2.0.0a1",
"versionType": "semver"
}
]
}
],
"source": "cve-coordination@google.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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."
}
],
"id": "CVE-2026-115522",
"lastModified": "2026-10-28T15:21:31.673",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityRequirement": "NOT_DEFINED",
"exploitMaturity": "NOT_DEFINED",
"integrityRequirement": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
"modifiedSubIntegrityImpact": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "cve-coordination@google.com",
"type": "Secondary"
}
]
},
"published": "2026-10-28T05:16:59.833",
"references": [
{
"source": "cve-coordination@google.com",
"url": "https://github.com/google/adk-python/commit/0ae2bffdd2628af6c8643bc4fd40c2f49f0c6bd4"
},
{
"source": "cve-coordination@google.com",
"url": "https://github.com/google/adk-python/commit/c27d8688ed9ea619587ad96cbfd641c34dd7340c"
},
{
"source": "cve-coordination@google.com",
"url": "https://github.com/google/adk-python/commit/f72f0db58c5c1f4e8b8d4f04b8c592c9e49cbe9e"
},
{
"source": "cve-coordination@google.com",
"url": "https://github.com/google/adk-python/issues/5618"
},
{
"source": "cve-coordination@google.com",
"url": "https://github.com/google/adk-python/pull/5619"
},
{
"source": "cve-coordination@google.com",
"url": "https://github.com/google/adk-python/releases/tag/v1.39.1"
},
{
"source": "cve-coordination@google.com",
"url": "https://github.com/google/adk-python/releases/tag/v2.7.0"
}
],
"sourceIdentifier": "cve-coordination@google.com",
"vulnStatus": "Awaiting Analysis",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-668"
}
],
"source": "cve-coordination@google.com",
"type": "Secondary"
}
]
}
}
}
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.