CVE-2026-22744 json
Spring AI Redis Store has TAG Field Query Injection Through Improper Neutralization of Special Characters
published 2026-03-27 7 mo ago modified 2026-10-26 13 d ago also GHSA-44f4-gvwj-6qg3 , EUVD-2026-16541
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
In RedisFilterExpressionConverter of spring-ai-redis-store, when a user-controlled string is passed as a filter value for a TAG field, stringValue() inserts the value directly into the @field:{VALUE} RediSearch TAG block without escaping characters.This issue affects Spring AI: from 1.0.0 before 1.0.5, from 1.1.0 before 1.1.4.
Patch / fix
- maven org.springframework.ai:spring-ai-redis-store 1.0.5, 1.1.4
- Spring Spring AI 1.0.5, 1.1.4
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.ai:spring-ai-redis-store | >=1.0.0-M5, <1.0.5 >=1.1.0-M1, <1.1.4 |
1.0.5 1.1.4 |
Affected products
- Spring Spring AI
Classification
References
-
github.com
/spring-projects/spring-ai/commit/707e990c9152aabb9c9226053725efa2ada72223
web
-
spring.io
/security/cve-2026-22744
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-22744
advisory
-
github.com
/spring-projects/spring-ai
package
-
github.com
/spring-projects/spring-ai/releases/tag/v1.0.5
web
-
github.com
/spring-projects/spring-ai/releases/tag/v1.1.4
web
Sources
- CVE List CVE-2026-22744
- GitHub Advisory GHSA-44f4-gvwj-6qg3
- NVD CVE-2026-22744
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.