dbcve.org
Spring AiFramework / library · VMware

CVE-2026-22744

HIGH · 7.5 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 1.0.5 / 1.1.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Spring AI's RedisStore module, the RedisFilterExpressionConverter's stringValue() method directly injects user-provided TAG field values into RediSearch queries (@field:{VALUE}) without escaping special characters. This allows attackers to manipulate RediSearch TAG queries through specially crafted input, potentially enabling injection attacks against the RediSearch backend.

MitigationUpgrade Spring AI to version 1.0.5 or 1.1.4 or later, which should include proper escaping of special characters in TAG field values before insertion into RediSearch queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring AiFramework / library
Affected:>= 1.0.0, < 1.0.5>= 1.1.0, < 1.1.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Spring AI version
    Inspect your project's dependency manifest (Maven pom.xml, Gradle build.gradle, or runtime classpath) for the spring-ai-core or spring-ai-redis dependency version
    Affected if version is >= 1.0.0 and < 1.0.5 OR >= 1.1.0 and < 1.1.4
  2. Confirm RedisStore module is in use
    Search your codebase for imports or references to org.springframework.ai.redis.store.RedisStore or related Redis vector store classes
    Affected if RedisStore or related Redis vector store classes are used in the application
  3. Verify RediSearch backend is enabled
    Check your Redis configuration or running services to confirm RediSearch (FT commands) or Redis Stack is deployed; look for RediSearch indexes via FT._LIST or FT.INFO
    Affected if RediSearch is enabled as the search backend
  4. Identify TAG field usage in the schema
    Review your RediSearch schema definition (FT.CREATE) or Spring AI configuration for any TAG fields used in indexed document properties
    Affected if TAG fields are defined in the RediSearch schema and used for filtering
  5. Trace user input to stringValue method
    Review code paths where user-provided values are passed to RedisFilterExpressionConverter.stringValue() or used in filter expressions with the RedisStore; examine any search/filter APIs that accept user input
    Affected if Untrusted or user-controlled input can reach the vulnerable stringValue() method in RedisFilterExpressionConverter for RediSearch TAG queries

Your environment is affected if you run a vulnerable Spring AI version (1.0.0-1.0.4 or 1.1.0-1.1.3), use the RedisStore module with RediSearch, and allow user input to flow into TAG field queries without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.5 / 1.1.4 or later
Fixed in 1.0.51.1.4
Interim mitigation

Upgrade Spring AI to version 1.0.5 or 1.1.4 or later, which should include proper escaping of special characters in TAG field values before insertion into RediSearch queries.

Recommended fix High confidence

1.0.5 for 1.0.x users; 1.1.4 (or latest 1.1.x) for 1.1.x users

  1. Identify the current Spring AI version by checking project dependencies (pom.xml, build.gradle, or similar)
  2. If using Spring AI 1.0.x (version >= 1.0.0 and < 1.0.5), upgrade to version 1.0.5
  3. If using Spring AI 1.1.x (version >= 1.1.0 and < 1.1.4), upgrade to version 1.1.4
  4. Alternatively, upgrade to the latest stable 1.1.x release (1.1.4 or higher)
  5. Rebuild the project with the updated dependency version
  6. Run application tests to verify the fix works and no regressions were introduced

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Ai Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing5.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,070
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,312.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22744 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22744 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data