CVE-2026-59319

Analyzed Analyzed - Analysis Complete

RedisChatMemoryRepository Metadata Injection via Unescaped RediSearch Queries

Publication date: 2026-08-27

Last updated on: 2026-08-31

Assigner: VMware

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-27

Last Modified

2026-08-31

Generated

2026-09-17

AI Q&A

2026-08-28

EPSS Evaluated

2026-09-15

NVD

CVE-2026-59319

Affected Vendors & Products

Vendor	Product	Version / Range
vmware	spring_ai	From 2.0.0 (inc) to 2.0.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-943	The product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.

Attack-Flow Graph

Executive Summary

This is a tag injection vulnerability in Spring AI's RedisChatMemoryRepository component. The findByMetadata() method builds RediSearch queries from user-supplied metadata without proper escaping, unlike other methods in the same class. Attackers can inject RediSearch syntax like 'x} | *' to bypass tag constraints and retrieve all chat messages across every conversation in the index.

Detection Guidance

Check if your Spring AI application uses RedisChatMemoryRepository with version 2.0.0. Inspect logs for unusual RediSearch query patterns or unauthorized access to chat messages. No specific commands are provided in the context.

Impact Analysis

An attacker could exploit this to access all chat messages stored in the Redis index, potentially exposing sensitive conversation data across multiple conversations. This could lead to unauthorized data disclosure or privacy violations depending on the application's use case.

Compliance Impact

This vulnerability could violate data protection regulations like GDPR (Article 32 security of processing) or HIPAA (Security Rule) by enabling unauthorized access to personal or protected health information stored in chat messages. Organizations using affected versions may face compliance violations and potential fines.

Mitigation Strategies

Upgrade Spring AI to version 2.0.1 (OSS) or 2.0.0.1 (Enterprise) immediately. If upgrading is not possible, restrict access to the findByMetadata() method or apply input validation to prevent RediSearch syntax injection.

Hi! I’m here to help you understand CVE-2026-59319. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70