Quick answers
- Is CVE-2026-22744 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-22744 being exploited in the wild.
- How severe is CVE-2026-22744?
- High severity, with a CVSS score of 7.5, published 27 March 2026.
- Which products and versions are affected?
- org.springframework.ai:spring-ai-redis-store (Maven) ECOSYSTEM:introduced=1.0.0-M5,fixed=1.0.5; VMware Spring Ai 1.0.0 to 1.0.4, 1.1.0 to 1.1.3.
- Is there a fix for CVE-2026-22744?
- Yes. org.springframework.ai:spring-ai-redis-store (Maven): upgrade to 1.0.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-22744 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-22744?
- Check whether you run org.springframework.ai:spring-ai-redis-store (Maven) or VMware Spring Ai at an affected version. 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.
How to fix
- org.springframework.ai:spring-ai-redis-store (Maven): upgrade to 1.0.5 or later
# set org.springframework.ai:spring-ai-redis-store to 1.0.5 in your pom.xml or build.gradle
Technical details
An injection vulnerability exists in the 'spring-ai-redis-store' component of Spring AI. The 'RedisFilterExpressionConverter.stringValue()' method fails to properly escape user-controlled strings before inserting them into the '@field:{VALUE}' RediSearch TAG block. A remote attacker can exploit this by providing malicious filter values, potentially leading to unauthorized data retrieval or manipulation of search logic. The issue is fixed in Spring AI versions 1.0.5 and 1.1.4.
Affected products
- VMware Spring AI 1.0.0 to 1.0.4, 1.1.0 to 1.1.3
Identifiers
- CVE-2026-22744
- GHSA-44f4-gvwj-6qg3
Timeline
- 2026-03-27: disclosed: Initial advisory published by VMware
- 2026-03-27: advisory