# CVE-2026-40978: Spring AI has SQL Injection in CosmosDBVectorStore.doDelete() > Attackers can execute arbitrary SQL queries via crafted document IDs in Spring AI's CosmosDBVectorStore, potentially reading or modifying data. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 28 Apr 2026 - **Updated:** 29 Apr 2026 - **Also known as:** GHSA-63c8-m9m2-cvr3 ## What is CVE-2026-40978? CVE-2026-40978 is a high-severity SQL injection vulnerability in Spring AI, published on 28 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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) Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) ## Which versions are affected by CVE-2026-40978? 4 open source packages ship an affected version, including org.springframework.ai:spring-ai-azure-cosmos-db-store. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.ai:spring-ai-azure-cosmos-db-store` | Maven | From 1.0.0 | 1.0.6 | | `org.springframework.ai:spring-ai-azure-cosmos-db-store` | Maven | From 1.0.0 | 1.0.6 | | `org.springframework.ai:spring-ai-azure-cosmos-db-store` | Maven | From 1.1.0 | 1.1.5 | | `org.springframework.ai:spring-ai-azure-cosmos-db-store` | Maven | From 1.1.0 | 1.1.5 | Products: Vmware Spring Ai. ## How do I fix CVE-2026-40978? Upgrade org.springframework.ai:spring-ai-azure-cosmos-db-store to a fixed version for your release line: 1.0.6 or 1.1.5. ## Is CVE-2026-40978 being exploited? There is no known exploitation of CVE-2026-40978 in the wild and no public exploit code. ## Other vulnerabilities in Spring AI - [CVE-2026-22738](https://insights.sbomify.com/CVE-2026-22738/): SpEL Injection via Unescaped Filter Key in SimpleVectorStore Leads to Remote Code Execution (critical 9.8) - [CVE-2026-22730](https://insights.sbomify.com/CVE-2026-22730/): CVE-2026-22730: SQL Injection in Spring AI MariaDBFilterExpressionConverter (high 8.8) - [CVE-2026-47835](https://insights.sbomify.com/CVE-2026-47835/): Spring AI vector store metadata filtering to handle special characters in Elasticsearch, OpenSearch, and GemFire Vector Stores (high 8.6) - [CVE-2026-41705](https://insights.sbomify.com/CVE-2026-41705/): Spring AI's MilvusVectorStore#doDelete(List) implementation is vulnerable to filter-expression injection via unsanitized document IDs (high 8.6) - [CVE-2026-40967](https://insights.sbomify.com/CVE-2026-40967/): Spring AI has a VectorStore FilterExpression Converter injection (high 8.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-40978 and fix it if it is affected. What it is: CVE-2026-40978 is a high-severity SQL injection vulnerability in Spring AI, published on 28 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-40978 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.ai:spring-ai-azure-cosmos-db-store (Maven): affected from 1.0.0; fixed in 1.0.6 - org.springframework.ai:spring-ai-azure-cosmos-db-store (Maven): affected from 1.0.0; fixed in 1.0.6 - org.springframework.ai:spring-ai-azure-cosmos-db-store (Maven): affected from 1.1.0; fixed in 1.1.5 - org.springframework.ai:spring-ai-azure-cosmos-db-store (Maven): affected from 1.1.0; fixed in 1.1.5 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-40978/ (Markdown: https://insights.sbomify.com/CVE-2026-40978/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40978 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40978 - OSV: https://osv.dev/vulnerability/CVE-2026-40978 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-40978/ Summaries are generated and may contain mistakes; the official description above is the record.