Spring AI 2.0.0
Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
| Link | Providers |
|---|---|
| https://spring.io/security/cve-2026-59319 |
|
Fri, 28 Aug 2026 08:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Spring
Spring spring Ai |
|
| Vendors & Products |
Spring
Spring spring Ai |
Fri, 28 Aug 2026 07:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-20 |
Thu, 27 Aug 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | RedisChatMemoryRepository.findByMetadata() builds RediSearch tag and text queries from caller-supplied metadata values without applying RediSearchUtil.escape(), unlike get(), clear(), and findByTimeRange() in the same class which do escape their inputs. An application that passes user-controlled values to findByMetadata() on a tag-typed metadata field allows an attacker to inject RediSearch syntax (e.g. x} | *) that breaks out of the tag clause and matches all indexed chat messages across every conversation in the index. Spring AI 2.0.0 | |
| Title | RediSearch Tag Injection in RedisChatMemoryRepository Allows Cross-Conversation Data Exposure | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: vmware
Published:
Updated: 2026-08-27T18:04:46.944Z
Reserved: 2026-07-04T18:14:10.167Z
Link: CVE-2026-59319
No data.
Status : Awaiting Analysis
Published: 2026-08-27T20:17:57.913
Modified: 2026-08-28T18:47:30.163
Link: CVE-2026-59319
No data.
OpenCVE Enrichment
Updated: 2026-08-28T08:30:16Z
-
CWE-20
Improper Input Validation