Spring AiFramework / library · VMware
CVE-2026-40967
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 · uneditedIn Spring AI, various FilterExpressionConverter implementations accept a filter expression object and translate them to specific vector store query languages. In several cases, keys and values are not properly escaped, leading to the ability to alter the query. Affected versions: Spring AI: 1.0.0 - 1.0.5 (fixed in 1.0.6), 1.1.0 - 1.1.4 (fixed in 1.1.5)
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 · moderate confidenceSpring AI's FilterExpressionConverter implementations fail to properly escape keys and values when translating filter expression objects into vector store query languages. This improper input handling allows attackers to inject or alter query syntax, potentially enabling unauthorized data access or manipulation of vector database operations.
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
>= 1.0.0, < 1.0.6>= 1.1.0, < 1.1.5CVSS 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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Spring AI versionInspect the spring-ai-core JAR file MANIFEST.MF or check your Maven pom.xml/Gradle build.gradle for the org.springframework.ai:spring-ai-core dependency version.Affected if The version is >= 1.0.0 and < 1.0.6, or >= 1.1.0 and < 1.1.5
-
Identify vector store dependenciesReview your project's pom.xml or build.gradle for vector store dependencies such as spring-ai-chroma-store, spring-ai-pinecone-store, spring-ai-milvus-store, or similar spring-ai-*store libraries.Affected if Any vector store dependency from Spring AI is present in the project
-
Verify FilterExpressionConverter usageSearch your codebase for imports or references to FilterExpressionConverter, org.springframework.ai.vectorstore.filter.FilterExpression, or classes implementing FilterExpressionConverter.Affected if FilterExpressionConverter or filter expression classes are being used in your code
-
Check for dynamic filter input handlingInspect code paths where filter expressions are constructed, particularly where user-supplied input (request parameters, API payloads, user data) flows into filter expression builders.Affected if Filter expressions accept dynamic or user-provided keys or values without validation
-
Review vector store query configurationExamine your vector store configuration beans and any custom FilterExpressionConverter implementations or extensions that handle query translation.Affected if Custom filter logic or direct vector store queries are implemented
You are affected if your Spring AI version falls within the vulnerable ranges AND you use vector store functionality with filter expressions that could contain unsanitized input.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.61.1.5
Upgrade Spring AI to version 1.0.6 or 1.1.5 or later which contains the fix for proper escaping in FilterExpressionConverter implementations. If immediate upgrade is not feasible, implement input validation and sanitization on all filter expression inputs before they reach the converters.
Upgrade to Spring AI 1.0.6 or 1.1.5 (choose the appropriate release line based on your current major.minor version)
- Identify your current Spring AI version in your project's dependency management (pom.xml or build.gradle)
- For Maven projects, locate the <spring-ai.version> property or the direct spring-ai dependencies in pom.xml
- For Gradle projects, locate the springAiVersion or dependency declarations in build.gradle
- Update the Spring AI version to 1.0.6 if using the 1.0.x line, or to 1.1.5 if using the 1.1.x line
- Run mvn clean compile (Maven) or ./gradlew compileJava (Gradle) to verify the upgrade compiles successfully
- Run your project's test suite to ensure no breaking changes affect your application
- Redeploy the updated application to your runtime environment
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
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40967 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40967 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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