What is the CVSS score of CVE-2026-22730?

CVE-2026-22730 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Java are affected by CVE-2026-22730?

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…. A patch is available.

How to fix or mitigate CVE-2026-22730?

Within 24 hours: Inventory all systems using Spring AI with MariaDB backends and assess exposure; disable Spring AI MariaDB filtering features if possible. Within 7 days: Implement network segmentation to restrict database access, deploy WAF rules to detect SQL injection patterns, and enable enhanced database query logging and monitoring. Within 30 days: Establish continuous monitoring for suspicious database activities, develop an incident response plan specific to this vulnerability, and maintain weekly contact with Spring AI vendor for patch availability updates.

Java CVE-2026-22730

EUVD-2026-12797 HIGH

SQL Injection (CWE-89)

2026-03-18 vmware

GHSA-c267-rfvc-mvpm

Java SQLi

8.8

CVSS 3.1 · NVD

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

EUVD ID Assigned

Mar 18, 2026 - 08:00 euvd

EUVD-2026-12797

Analysis Generated

Mar 18, 2026 - 08:00 vuln.today

CVE Published

Mar 18, 2026 - 07:36 nvd

HIGH 8.8

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 maven packages depend on org.springframework.ai:spring-ai-mariadb-store (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 1.1.0-M1.

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.

AnalysisAI

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.

Technical ContextAI

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.

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.