CVE-2026-22730·MariaDB vulnerability
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.
- Severity
- high
- Software
- MariaDB
- Fixed in
- 1.1.3
- Published
- 2026-03-18
Affected versions
From: 1.1.0
Until: 1.1.3
Fixed in: 1.1.3
How to fix this CVE
Update MariaDB to version 1.1.3 or later to patch the SQL injection vulnerability in the Spring AI filter expression converter. This fix removes the missing input sanitization that allowed authenticated users to bypass access controls and execute arbitrary SQL commands. Apply the update immediately, especially in environments where Spring AI is integrated with MariaDB for vector search or AI-driven features.
sudo dnf update mariadb-serverDefensia detects this vulnerability
What an exploitation attempt looks like
Sample log line indicative of exploitation attempts:
SQL injection payloads in MariaDB query logs containing metadata filter expressions with embedded UNION SELECT, time-based delays (SLEEP/BENCHMARK), or boolean-based conditions; example pattern: `UNION.*SELECT|BENCHMARK\(.*,.*\)|AND.*=.*--` in authenticated query logsWAF mitigation (if patching is not yet possible)
Add this rule to your WAF to block exploitation attempts while you schedule the patch.
If MariaDB is exposed through a web application layer, implement WAF rules to reject API requests containing SQL metacharacters (UNION, SELECT, --, /*, ;) in filter parameters; additionally, enforce strict input validation on all metadata-driven query endpoints and use parameterized queries exclusively.How to check if you are affected
- Run `mariadb --version` or `SELECT VERSION();` in the MariaDB client to confirm the installed version. Vulnerable versions range from 1.1.0 to 1.1.2.
- Check if Spring AI is installed and configured with MariaDB by searching for Spring AI dependencies in your application's pom.xml or build.gradle: `grep -r 'spring-ai' /path/to/app`
- Search MariaDB query logs for suspicious SQL patterns combining filter expressions with UNION, subqueries, or comment sequences (-- or /* */) in authenticated sessions: `grep -i 'UNION\|--\|/\*' /var/log/mysql/mysql.log`
- After updating, verify the fix by running `mariadb --version` again and confirming the version is 1.1.3 or later, then restart the MariaDB service: `sudo systemctl restart mariadb`
FAQ
What is CVE-2026-22730?
CVE-2026-22730 is a SQL injection vulnerability in Spring AI's MariaDB filter expression converter that allows authenticated users to craft malicious metadata queries and execute arbitrary SQL commands, bypassing role-based access controls.
Is CVE-2026-22730 being actively exploited?
No, this vulnerability is not currently listed in CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, the attack requires only valid database credentials, so it should be prioritized in internal threat scenarios.
What versions of MariaDB are affected by CVE-2026-22730?
Spring AI versions 1.1.0 through 1.1.2 are vulnerable when integrated with MariaDB. The vulnerability is patched in version 1.1.3 and later.
How do I check if my server is vulnerable to CVE-2026-22730?
Run `mariadb --version` to check the MariaDB version, and verify Spring AI version in your application build file. If Spring AI is between 1.1.0–1.1.2 and connected to MariaDB, your installation is vulnerable.
Does Defensia detect CVE-2026-22730?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If MariaDB is installed on a monitored server, CVE-2026-22730 will appear in your dashboard with remediation steps.
Related MariaDB CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-22730. Free for 1 server.
Get started free