dbcve.org
Spring AiFramework / library · VMware

CVE-2026-22743

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
Spring AI's spring-ai-neo4j-store contains a Cypher injection vulnerability in Neo4jVectorFilterExpressionConverter. When a user-controlled string is passed as a filter expression key in Neo4jVectorFilterExpressionConverter of spring-ai-neo4j-store, doKey() embeds the key into a backtick-delimited Cypher property accessor (node.`metadata.`) after stripping only double quotes, without escaping embedded backticks.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

This is a Cypher injection vulnerability in Spring AI's Neo4jVectorFilterExpressionConverter. The doKey() method takes user-controlled strings as filter expression keys and embeds them into backtick-delimited Cypher property accessors (node.`metadata.`). It only strips double quotes without escaping embedded backticks, allowing attackers to inject malicious Cypher syntax by including backticks in the key.

MitigationUpgrade to Spring AI version 1.0.5 or 1.1.4 or later which should contain proper backtick escaping. As a temporary workaround, validate and sanitize all user input before passing to Neo4jVectorFilterExpressionConverter.

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 Spring AI version in use
    Check your project's dependency management file (pom.xml, build.gradle, or equivalent) for the spring-ai-core or spring-ai-neo4j-vectorstore dependency and note its version.
    Affected if The installed version falls within >= 1.0.0, < 1.0.5 or >= 1.1.0, < 1.1.4.
  2. Verify Neo4j vector store is configured
    Search your codebase for imports or references to Neo4jVectorStore, Neo4jVectorFilterExpressionConverter, or similar Neo4j vector-related classes.
    Affected if Your application uses Neo4j as a vector store and imports or instantiates Neo4jVectorFilterExpressionConverter.
  3. Check for filter expression usage in vector searches
    Search your codebase for calls to vector store search methods that accept filter parameters, particularly code passing user-controlled input to filter expressions.
    Affected if Your application passes user input as keys in filter expressions to Neo4j vector searches.
  4. Inspect the Neo4jVectorFilterExpressionConverter implementation
    Locate the Neo4jVectorFilterExpressionConverter class in your Spring AI library JAR and examine the doKey() method to confirm it only strips double quotes without escaping backticks.
    Affected if The doKey() method uses backtick-delimited property accessors (node.`property`) and lacks backtick escaping logic.

You are affected if your environment uses Spring AI versions 1.0.0 through 1.0.4 or 1.1.0 through 1.1.3 with Neo4j vector store and passes untrusted user input into filter expression keys.

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 to Spring AI version 1.0.5 or 1.1.4 or later which should contain proper backtick escaping. As a temporary workaround, validate and sanitize all user input before passing to Neo4jVectorFilterExpressionConverter.

Recommended fix High confidence

Spring AI 1.0.5 or 1.1.4 (depending on your current major.minor line)

  1. 1. Identify your current Spring AI version by checking your dependency management (e.g., pom.xml, build.gradle, or your project's dependency lock file
  2. 2. If using Spring AI 1.0.x (versions 1.0.0-1.0.4), upgrade to version 1.0.5 by updating the spring-ai.version property or dependency to 1.0.5
  3. 3. If using Spring AI 1.1.x (versions 1.1.0-1.1.3), upgrade to version 1.1.4 by updating the spring-ai.version property or dependency to 1.1.4
  4. 4. Rebuild and test your application to ensure the upgrade does not introduce issues
  5. 5. If using spring-ai-neo4j-store, verify that the Neo4jVectorFilterExpressionConverter is no longer vulnerable to Cypher injection via filter expression keys
Caveat This appears to be a security patch release; breaking changes are unlikely but review the 1.0.5 and 1.1.4 release notes for any changes that may affect your application

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

Fix this in Spring Ai Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22743 — 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-22743 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