VMwareCVE-2026-59319
VMware Spring AI: attacker could inject RediSearch syntax
Medium4.3CVE-2026-59319 · Published Aug 27, 2026 · updated Aug 31, 2026
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
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| Spring AI Product | <= 2.0.0 | No fix yet |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- Severity from
- the vendor (its own CVE record or advisory)
- Weakness
- CWE-943
More VMware advisories
All VMware| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Aug 27 | VMware Spring AMQP: resource leak | Medium6.5 | No fix yet |
| Aug 27 | VMware Spring Integration: race condition | Medium4.2 | No fix yet |
| Aug 27 | VMware Spring Integration: improper input validation | Medium6.3 | No fix yet |
| Aug 27 | VMware Spring Integration: race condition | High8.2 | No fix yet |
| Aug 27 | VMware Spring Integration: unsafe deserialization | High8.0 | No fix yet |
| Aug 27 | VMware Spring Integration: link following | Medium6.8 | No fix yet |