Cross-context response disclosure via truncated prompt hash
Published Aug 21, 2026 · Updated Aug 21, 2026
Cache isolation failure in Spring AI 2.0.0 allows remote authenticated users to receive responses cached for unrelated system prompts. The Semantic Cache context-key path truncates a SHA-256 digest of the system prompt, allowing distinct prompts to share a cache partition. Exploitation requires Semantic Cache, separate trust contexts represented by different system prompts, and attacker-controlled queries; consequences are limited to returned cached content and response integrity.
Summary
What happened
Cache isolation failure in Spring AI 2.0.0 allows remote authenticated users to receive responses cached for unrelated system prompts. The Semantic Cache context-key path truncates a SHA-256 digest of the system prompt, allowing distinct prompts to share a cache partition. Exploitation requires Semantic Cache, separate trust contexts represented by different system prompts, and attacker-controlled queries; consequences are limited to returned cached content and response integrity.
The record
- CVE
- CVE-2026-59308
- Published
- Aug 21, 2026
- Updated
- Aug 21, 2026
- Vendor
- Spring
- Product
- Spring AI
- Classifications
- CWE-668
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo