CVE-2026-59308 Semantic Cache Cross-Tenant Isolation Bypass via SHA-256 Truncation
Attackers can access cached responses from unrelated contexts due to weak hash isolation in Spring AI's Semantic Cache.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-59308?
CVE-2026-59308 is a medium-severity vulnerability in Spring AI, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
In Spring AI's Semantic Cache support, the context hash used to isolate cached responses between different system prompts could allow cached responses to be shared across unrelated contexts. Affected versions: Spring AI: 2.0.0
Weakness: CWE-668
Which versions are affected by CVE-2026-59308?
It affects 1 product.
Products include Vmware Spring Ai.
How do I fix CVE-2026-59308?
No fix has been published for CVE-2026-59308 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-59308 being exploited?
There is no known exploitation of CVE-2026-59308 in the wild and no public exploit code.
Other vulnerabilities in Spring AI
- CVE-2026-22738 SpEL Injection via Unescaped Filter Key in SimpleVectorStore Leads to Remote Code Execution
- CVE-2026-40978 Spring AI has SQL Injection in CosmosDBVectorStore.doDelete()
- CVE-2026-22730 CVE-2026-22730: SQL Injection in Spring AI MariaDBFilterExpressionConverter
- CVE-2026-47835 Spring AI vector store metadata filtering to handle special characters in Elasticsearch, OpenSearch, and GemFire Vector Stores
- CVE-2026-41705 Spring AI's MilvusVectorStore#doDelete(List) implementation is vulnerable to filter-expression injection via unsanitized document IDs
Sources
Also known as GHSA-h4jw-w55g-65gf.