dbcve.org
Spring AiFramework / library · VMware

CVE-2026-40978

HIGH · 8.8 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 1.0.6 / 1.1.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
SQL injection vulnerability in Spring AI's `CosmosDBVectorStore` allows attackers to execute arbitrary SQL queries via crafted document IDs. 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 · high confidence

SQL injection vulnerability in Spring AI's CosmosDBVectorStore allows execution of arbitrary SQL queries via unsanitized document IDs passed to the vector store. Attackers can craft malicious document IDs that bypass input validation and inject SQL commands directly into the underlying Azure Cosmos DB queries.

MitigationUpgrade Spring AI to version 1.0.6 or 1.1.5 or later. Additionally, implement strict input validation on all document IDs before passing them to the VectorStore to defense-in-depth.

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.6>= 1.1.0, < 1.1.5

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Identify Spring AI version in use
    Inspect your project's dependency management file (pom.xml, build.gradle, or equivalent) for the spring-ai-core or spring-ai-azure-openai artifact and note its version number
    Affected if The version falls within >= 1.0.0 and < 1.0.6, or >= 1.1.0 and < 1.1.5
  2. Confirm CosmosDBVectorStore is in use
    Search project source code for imports or references to org.springframework.ai.vectorstore.CosmosDbVectorStore or com.azure.spring.data.cosmosdb.core.mapping.Container annotations
    Affected if CosmosDBVectorStore is imported, instantiated, or configured in the application code
  3. Check for vector store configuration
    Examine application configuration files (application.yml, application.properties) for spring.ai.vectorstore.cosmos.* properties or custom CosmosDbVectorStore bean definitions
    Affected if A CosmosDB vector store is configured with connection details to Azure Cosmos DB
  4. Verify document ID input handling
    Review code paths where document IDs are set on documents before calling vectorStore.add() or vectorStore.delete() - look for direct assignment of user-supplied strings to document.getId()
    Affected if External or user-controlled input is directly assigned to document IDs without sanitization before vector store operations

You are affected if your application uses a vulnerable Spring AI version (1.0.0-1.0.5 or 1.1.0-1.1.4) AND utilizes CosmosDBVectorStore with document IDs derived from untrusted input.

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.6 / 1.1.5 or later
Fixed in 1.0.61.1.5
Interim mitigation

Upgrade Spring AI to version 1.0.6 or 1.1.5 or later. Additionally, implement strict input validation on all document IDs before passing them to the VectorStore to defense-in-depth.

Recommended fix High confidence

Spring AI 1.0.6 or 1.1.5 (whichever version line you're on)

  1. Locate your project's build configuration file (pom.xml for Maven or build.gradle for Gradle)
  2. If using Spring Boot parent dependency management, update the spring-ai.version property to 1.0.6 (for 1.0.x line) or 1.1.5 (for 1.1.x line)
  3. Alternatively, directly update the spring-ai-starter-... dependency version to match your chosen release line
  4. Run mvn clean compile or ./gradlew build to verify the upgrade resolves the dependency
  5. Test the CosmosDBVectorStore functionality to confirm the SQL injection fix is working as expected
Caveat Review the Spring AI release notes for your target version to check for any breaking changes in your specific usage of CosmosDBVectorStore

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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