Skip to main content

Spring Ai CVE-2026-22730

| EUVDEUVD-2026-12797 HIGH
SQL Injection (CWE-89)
2026-03-18 vmware GHSA-c267-rfvc-mvpm
8.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to Spring AI application
  2. Delivery
    Submit crafted filter expression to MariaDBFilterExpressionConverter
  3. Exploit
    Inject malicious SQL via unsanitized input
  4. Execution
    Bypass metadata access controls
  5. Persist
    Execute arbitrary SQL commands
  6. Impact
    Extract or modify sensitive database records

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires authenticated user access to Spring AI applications using MariaDBFilterExpressionConverter for metadata filtering. Attacker must have PR:L privileges to inject malicious SQL through filter expressions. No victim interaction needed. Affects default Spring AI deployments with MariaDB backend.

Impact

This vulnerability presents significant real-world risk due to multiple converging factors from the CVSS vector analysis. The attack vector is network-based (AV:N) with low complexity (AC:L), requiring only low privileges (PR:L) and no user interaction (UI:N), making it highly accessible to authenticated attackers. The impact is severe across all CIA triad dimensions (C:H/I:H/A:H), enabling complete database compromise. While EPSS probability data is not provided in the intelligence, the combination of low attack complexity, network accessibility, and critical impact typically correlates with elevated exploitation likelihood. No KEV listing is mentioned, suggesting no confirmed active exploitation in the wild yet, and no public POC is explicitly referenced. However, SQL injection vulnerabilities are well-understood and easily exploitable once discovered, making this automatable and likely to be weaponized rapidly. The SSVC framework would likely classify this as requiring urgent remediation due to the technical impact (total system compromise possible), low exploitation barrier, and broad attack surface in internet-facing Java applications using Spring AI with MariaDB backends.

Exploit ScenarioDerived

An authenticated attacker with low-level credentials to a Spring AI application crafts a malicious metadata filter expression containing SQL injection payloads when querying the MariaDB vector database. Because the MariaDBFilterExpressionConverter fails to sanitize this input, the attacker's injected SQL commands execute with the privileges of the application's database user, allowing them to bypass intended access controls, extract sensitive data from other users' records, modify or delete database contents, or potentially escalate to operating system command execution depending on database configuration. Given the network-accessible attack vector and low complexity, this can be performed remotely without user interaction once the attacker has obtained valid application credentials.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 18, 2026

A critical SQL injection vulnerability in Spring AI's MariaDBFilterExpressionConverter component allows authenticated attackers to bypass metadata-based access controls and execute arbitrary SQL commands due to missing input sanitization. VMware Spring AI versions 1.0.x prior to 1.0.4 and 1.1.x prior to 1.1.3 are affected. With a CVSS score of 8.8, this vulnerability enables attackers with low-level privileges to compromise confidentiality, integrity, and availability of the database system through network-based attacks with low complexity.

RemediationAI

Immediately upgrade VMware Spring AI to version 1.0.4 or later for the 1.0.x branch, or to version 1.1.3 or later for the 1.1.x branch as detailed in the official VMware Spring security advisory at https://spring.io/security/cve-2026-22730. Review all application code utilizing MariaDBFilterExpressionConverter to identify potential attack surfaces where user-controlled input influences filter expressions. Until patching is completed, implement defense-in-depth measures including strict input validation at the application layer using allowlists for filter expression parameters, enforce principle of least privilege for database accounts used by Spring AI applications to limit blast radius of SQL injection attacks, deploy web application firewall (WAF) rules to detect and block SQL injection patterns, and monitor database query logs for suspicious activity or anomalous SQL commands that might indicate exploitation attempts. Consult the EUVD advisory at https://nvd.nist.gov/vuln/detail/CVE-2026-22730 for additional technical details and the VulDB entry at https://vuldb.com/?id.351507 for community-contributed indicators of compromise.

Affected VersionsENISA

Spring AI 1.0.x <1.0.4
Spring AI 1.1.x <1.1.3

Affected Packages

maven org.springframework.ai:spring-ai-mariadb-store fix: 1.0.4, 1.1.3
euvd spring_ai fix: 1.0.4, 1.1.3

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in maven, euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Spring AI is VMware's framework for building AI applications in Java, and this vulnerability affects its MariaDB integration component specifically within the MariaDBFilterExpressionConverter class (CPE: cpe:2.3:a:vmware:spring_ai:*:*:*:*:*:*:*:*). The vulnerability stems from improper neutralization of special elements used in SQL commands, a classic SQL injection flaw. The MariaDBFilterExpressionConverter is responsible for converting filter expressions into SQL queries when working with vector databases and metadata filtering, but fails to properly sanitize user-supplied input before incorporating it into SQL statements. This allows specially crafted filter expressions to break out of their intended context and inject arbitrary SQL code, bypassing the metadata-based access control mechanisms that rely on these filters to enforce data isolation and security policies.

Know when Spring Ai gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch released
Mar 31, 2026 - 21:13 nvd
Patch available
CVE Published
Mar 18, 2026 - 07:36 nvd
HIGH 8.8

DescriptionCVE.org

A critical SQL injection vulnerability in Spring AI's MariaDBFilterExpressionConverter allows attackers to bypass metadata-based access controls and execute arbitrary SQL commands.

The vulnerability exists due to missing input sanitization.

Executive ViewAI

Why It Matters

A high-severity SQL injection vulnerability in Spring AI's MariaDB component allows attackers to bypass access controls and execute unauthorized database commands, potentially compromising sensitive data and system integrity. Organizations using Spring AI with MariaDB databases face immediate risk of data breach and unauthorized access if exploited.

Business Impact: High
Compensating Controls

Disable Spring AI's MariaDB filter expression converter functionality until patch availability; implement Web Application Firewall (WAF) rules to block SQL injection payloads; restrict database network access through network segmentation and firewall rules; enable database query auditing and real-time alerting for anomalous SQL patterns; apply principle of least privilege to database service accounts; implement API rate limiting on Spring AI endpoints; monitor vendor security advisories for patch release.

Threat Intelligence Overview

EPSS Score
0.0%
Top 90% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

Related Vulnerabilities in Spring AI Filter Expression Injection

View all 2
CVE-2026-59318 CRITICAL
9.8 Aug 21

Incorrect authorization in Spring AI's tool-calling layer allows a tool that was never advertised to the current request

CVE-2026-22738 CRITICAL
9.8 Mar 27

Spring AI versions 1.0.0 through 1.0.4 and 1.1.0 through 1.1.3 allow unauthenticated remote code execution through Sprin

CVE-2026-40978 HIGH
8.8 Apr 28

SQL injection in Spring AI's CosmosDBVectorStore component (versions 1.0.0-1.0.5 and 1.1.0-1.1.4) enables authenticated

CVE-2026-40967 HIGH
8.6 Apr 28

Filter expression injection in Spring AI 1.0.0-1.0.5 and 1.1.0-1.1.4 allows remote unauthenticated attackers to manipula

CVE-2026-22742 HIGH
8.6 Mar 27

Server-Side Request Forgery in Spring AI Bedrock Converse module enables unauthenticated remote attackers to force the a

CVE-2026-41705 HIGH
8.6 May 09

Filter-expression injection in Spring AI's MilvusVectorStore allows remote unauthenticated attackers to manipulate vecto

CVE-2026-41713 HIGH
8.2 May 12

Conversation memory poisoning in VMware Spring AI allows remote unauthenticated attackers to inject malicious input that

CVE-2026-47835 HIGH
7.5 Jun 15

Query injection in the Spring AI vector-store modules - spring-ai-elasticsearch-store, spring-ai-opensearch-store and sp

CVE-2026-59279 HIGH
7.5 Aug 21

Unbounded session accumulation in Spring AI 2.0.0's MCP Streamable HTTP server transport enables remote unauthenticated

CVE-2026-47851 HIGH
7.5 Aug 26

Denial of service in Spring AI's PDF document ingestion crashes the processing thread when parsing a crafted PDF with a

CVE-2026-47852 HIGH
7.5 Aug 26

Predictable ONNX model cache path creation in Spring AI enables a local attacker on a shared multi-user host to pre-crea

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy