Quick answers
- Is CVE-2026-59319 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59319 being exploited in the wild.
- How severe is CVE-2026-59319?
- Medium severity, with a CVSS score of 4.3, published 27 August 2026.
- Which products and versions are affected?
- Spring Spring AI 2.0.0.
- Is there a fix for CVE-2026-59319?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-59319 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59319?
- Check whether you run VMware Spring Ai. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a RediSearch query injection flaw in the findByMetadata() method of RedisChatMemoryRepository. The method constructs tag and text queries directly from caller-supplied metadata values without invoking RediSearchUtil.escape(), unlike other methods in the same class (get(), clear(), findByTimeRange()) that properly escape inputs. An attacker who provides user-controlled values to metadata parameters on tag-typed fields can inject RediSearch syntax operators (e.g., "x} | *") that escape the tag clause and match all indexed documents. The attack requires the ability to invoke findByMetadata() with attacker-controlled input, but does not require authentication or special privileges beyond application-level access. This allows unauthorized access to chat messages across all conversations in the Redis index.
Affected products
- Spring Spring AI 2.0.0
Timeline
- 2026-08-27: disclosed