Spring AiFramework / library · VMware
CVE-2026-22738
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, a SpEL injection vulnerability exists in SimpleVectorStore when a user-supplied value is used as a filter expression key. A malicious actor could exploit this to execute arbitrary code. Only applications that use SimpleVectorStore and pass user-supplied input as a filter expression key are affected. 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 confidenceA SpEL injection vulnerability in Spring AI's SimpleVectorStore allows attackers to execute arbitrary code by supplying malicious input used as filter expression keys. Only applications using SimpleVectorStore with user-controlled filter expression keys are affected.
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.5>= 1.1.0, < 1.1.4CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify Spring AI versionCheck your project's dependency management file (pom.xml, build.gradle, or similar) for the Spring AI version, or run 'mvn dependency:tree | grep spring-ai' or 'gradle dependencies | grep spring-ai'Affected if Version is >= 1.0.0 and < 1.0.5, or >= 1.1.0 and < 1.1.4
-
Verify SimpleVectorStore is in useSearch project codebase for imports or instantiation of 'SimpleVectorStore' class, such as 'import org.springframework.ai.vectorstore.SimpleVectorStore' or similar patternsAffected if SimpleVectorStore class is imported or instantiated in your code
-
Locate filter expression usageSearch for calls to SimpleVectorStore methods that accept filter expressions, such as 'filter', 'delete', or 'search' methods that take filter parametersAffected if Code contains calls to SimpleVectorStore filter-related methods
-
Inspect filter expression key handlingExamine how filter expression keys are populated - look for any place where user input (request parameters, API input, database values) is directly assigned to filter expression keys without sanitizationAffected if User-supplied or external input is passed directly as filter expression keys without validation or sanitization
You are affected if your Spring AI version falls within the vulnerable ranges AND you use SimpleVectorStore with user-supplied input as filter expression keys.
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.51.1.4
Upgrade Spring AI to version 1.0.5 or 1.1.4 or later. Until patched, avoid passing user-supplied input as filter expression keys in SimpleVectorStore.
Spring AI 1.0.5 or later (for 1.0.x users); Spring AI 1.1.4 or later (for 1.1.x users)
- Identify the current Spring AI version in your project (check pom.xml or build.gradle for the spring-ai-version or spring-ai-starter dependency version)
- If using Spring AI 1.0.x: upgrade to version 1.0.5 or later by updating the version property/dependency to 1.0.5
- If using Spring AI 1.1.x: upgrade to version 1.1.4 or later by updating the version property/dependency to 1.1.4
- After upgrading, rebuild and test your application to verify the SimpleVectorStore functionality still works correctly
- Ensure that user input is still properly validated before being used as filter expression keys, as a defense-in-depth practice
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
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 locallyCheck whether your project pulls in CVE-2026-22738 — 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-22738 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