cve.bz

CVE-2026-40978 vmware spring ai: SQL Injection

8.8 highEPSS 0.3%Fix available

High (8.8) in vmware spring ai. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.ai:spring-ai-azure-cosmos-db-store 1.0.6, 1.1.5.

On this page
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)

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-04-28. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-89 Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40978 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40978?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40978?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-40978 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-40978

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-40978](https://cve.bz/cve/badge/CVE-2026-40978.svg)](https://cve.bz/cve/CVE-2026-40978)

HTML:

<a href="https://cve.bz/cve/CVE-2026-40978"><img src="https://cve.bz/cve/badge/CVE-2026-40978.svg" alt="CVE-2026-40978"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring AIfrom 1.0.0 before 1.0.6
Spring AIfrom 1.1.0 before 1.1.5

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-63c8-m9m2-cvr3Mavenorg.springframework.ai:spring-ai-azure-cosmos-db-store>=1.0.0 <1.0.61.0.6
GHSA-63c8-m9m2-cvr3Mavenorg.springframework.ai:spring-ai-azure-cosmos-db-store>=1.1.0 <1.1.51.1.5

Attack patterns (CAPEC)

  • CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
  • CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
  • CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON