Unauthenticated TAG-filter bypass via unescaped values
Published Mar 27, 2026 · Updated Mar 27, 2026
Query injection in Spring AI 1.0.0 through 1.0.4 and 1.1.0 through 1.1.3 allows remote attackers to bypass RediSearch TAG filters. RedisFilterExpressionConverter.stringValue() concatenates the value into an @field:{VALUE} block without escaping RediSearch syntax. Exploitation requires an application to place attacker-controlled input in a TAG filter; injected syntax changes the query and exposes results excluded by the intended filter.
Summary
What happened
Query injection in Spring AI 1.0.0 through 1.0.4 and 1.1.0 through 1.1.3 allows remote attackers to bypass RediSearch TAG filters. RedisFilterExpressionConverter.stringValue() concatenates the value into an @field:{VALUE} block without escaping RediSearch syntax. Exploitation requires an application to place attacker-controlled input in a TAG filter; injected syntax changes the query and exposes results excluded by the intended filter.
The record
- CVE
- CVE-2026-22744
- Published
- Mar 27, 2026
- Updated
- Mar 27, 2026
- Vendor
- Spring
- Product
- Spring AI
- Classifications
- CWE-74, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 27, 2026CVE publishedPublication date reported by the CVE source.
- Mar 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <1.0.5
- Affected versionversion=1.1.0 <1.1.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo