# CVE-2026-59319: RediSearch Tag Injection in RedisChatMemoryRepository Allows Cross-Conversation Data Exposure

> Attackers can inject RediSearch syntax to expose chat messages from all conversations by exploiting unescaped metadata inputs in Spring AI.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-7r3j-5666-wc3c

## What is CVE-2026-59319?

CVE-2026-59319 is a medium-severity code injection vulnerability in Spring AI, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

## Which versions are affected by CVE-2026-59319?

It affects 1 product.


Products: Vmware Spring Ai.

## How do I fix CVE-2026-59319?

No fix has been published for CVE-2026-59319 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59319 being exploited?

There is no known exploitation of CVE-2026-59319 in the wild and no public exploit code.

## Other vulnerabilities in Spring AI

- [CVE-2026-22738](https://insights.sbomify.com/CVE-2026-22738/): SpEL Injection via Unescaped Filter Key in SimpleVectorStore Leads to Remote Code Execution (critical 9.8)
- [CVE-2026-40978](https://insights.sbomify.com/CVE-2026-40978/): Spring AI has SQL Injection in CosmosDBVectorStore.doDelete() (high 8.8)
- [CVE-2026-22730](https://insights.sbomify.com/CVE-2026-22730/): CVE-2026-22730: SQL Injection in Spring AI MariaDBFilterExpressionConverter (high 8.8)
- [CVE-2026-47835](https://insights.sbomify.com/CVE-2026-47835/): Spring AI vector store metadata filtering to handle special characters in Elasticsearch, OpenSearch, and GemFire Vector Stores (high 8.6)
- [CVE-2026-41705](https://insights.sbomify.com/CVE-2026-41705/): Spring AI's MilvusVectorStore#doDelete(List) implementation is vulnerable to filter-expression injection via unsanitized document IDs (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59319 and fix it if it is affected.

What it is: CVE-2026-59319 is a medium-severity code injection vulnerability in Spring AI, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59319 in the wild and no public exploit code.

Affected product: Spring AI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59319/ (Markdown: https://insights.sbomify.com/CVE-2026-59319/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59319
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59319
- OSV: https://osv.dev/vulnerability/CVE-2026-59319

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59319/
Summaries are generated and may contain mistakes; the official description above is the record.