Skip to main content
VulnerabilityPublished

CVE-2026-22730: VMware Spring AI · SQL Injection

Affects VMware Spring AISource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 1.1.3 or 1.0.4 soon.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.1.3, 1.0.4, 1.2.0 +1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Spring AI to 1.1.3 or 1.0.4; com.vmware/spring-ai to 1.2.0 or 1.1.0.

Affected software

ProductAffectedFixed in
VMwareSpring AIAffected
  • >=1.1.x <1.1.3
Fixed in
  • 1.1.3
VMwareSpring AIAffected
  • >=1.0.x <1.0.4
Fixed in
  • 1.0.4
Mavencom.vmware/spring-aipkg:maven/com.vmware/spring-aiOther threatsAffected
  • <1.1.0
  • >=1.0.0 <1.1.0
  • <1.2.0
  • >=1.1.0 <1.2.0
Fixed in
  • 1.1.0
  • 1.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-22730, organizations should: 1) Monitor VMware announcements closely and apply official patches immediately upon release. 2) Implement strict input validation and sanitization at all application layers interacting with the MariaDBFilterExpressionConverter. 3) Restrict database user privileges to the minimum necessary, avoiding use of high-privilege accounts for application queries. 4) Employ Web Application Firewalls (WAFs) with SQL injection detection rules tailored to Spring AI query patterns. 5) Conduct thorough code reviews and static analysis to identify and remediate similar injection flaws. 6) Monitor database logs for anomalous or unexpected query patterns indicative of injection attempts. 7) Segment AI infrastructure networks to limit lateral movement in case of compromise. 8) Educate developers on secure coding practices focusing on input sanitization and parameterized queries. These steps go beyond generic advice by focusing on compensating controls and proactive monitoring until patches are available.

Description

CVE-2026-22730 is a critical SQL injection vulnerability in VMware Spring AI versions 1.0.x and 1.1.x, specifically in the MariaDBFilterExpressionConverter component. This flaw arises from missing input sanitization, allowing attackers with limited privileges to bypass metadata-based access controls and execute arbitrary SQL commands. The vulnerability has a high CVSS score of 8.8, indicating severe impact on confidentiality, integrity, and availability without requiring user interaction. Although no known exploits are currently in the wild, the ease of exploitation and potential damage make it a significant threat. Organizations using affected Spring AI versions should prioritize patching once available and implement strict input validation and database access restrictions.

References

Community reviews

Loading reviews…