Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-22738: Vulnerability in Spring Spring AI

0
Critical
VulnerabilityCVE-2026-22738cvecve-2026-22738
Published: Fri Mar 27 2026 (03/27/2026, 05:21:07 UTC)
Source: CVE Database V5
Vendor/Project: Spring
Product: Spring AI

Description

CVE-2026-22738 is a critical remote code execution vulnerability in Spring AI's SimpleVectorStore component. It arises from a SpEL injection flaw when user-supplied input is used as a filter expression key. Exploitation requires no authentication or user interaction and can lead to full system compromise. The vulnerability affects Spring AI versions from 1. 0. 0 before 1. 0. 5 and 1. 1. 0 before 1.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/27/2026, 05:44:50 UTC

Technical Analysis

CVE-2026-22738 is a critical vulnerability identified in the Spring AI framework, specifically within the SimpleVectorStore component. The flaw is a SpEL (Spring Expression Language) injection vulnerability that occurs when user-supplied values are improperly used as filter expression keys without adequate validation or sanitization. This allows an attacker to inject malicious SpEL expressions, which the framework evaluates, leading to arbitrary code execution on the host system. The vulnerability affects Spring AI versions from 1.0.0 up to but not including 1.0.5, and from 1.1.0 up to but not including 1.1.4. Exploiting this vulnerability requires no authentication or user interaction, making it remotely exploitable over the network. The CVSS v3.1 base score is 9.8, reflecting its critical severity with high impact on confidentiality, integrity, and availability. The vulnerability is particularly dangerous because it allows attackers to execute arbitrary commands, potentially leading to full system compromise, data theft, or disruption of services. Although no known exploits have been reported in the wild yet, the simplicity of exploitation and the critical nature of the flaw necessitate urgent attention. The vulnerability is limited to applications that use SimpleVectorStore and pass user input as filter expression keys, so not all Spring AI deployments are affected. No official patches or mitigation links are provided in the data, indicating that users should monitor vendor advisories closely for updates.

Potential Impact

The impact of CVE-2026-22738 is severe for organizations using vulnerable versions of Spring AI with SimpleVectorStore configured to accept user-supplied filter keys. Successful exploitation can lead to remote code execution without authentication, allowing attackers to take full control of affected systems. This can result in data breaches, unauthorized access to sensitive information, disruption of AI services, and potential lateral movement within networks. Given Spring's widespread use in enterprise Java applications and the growing adoption of AI frameworks, the vulnerability poses a significant risk to industries relying on AI-driven applications, including finance, healthcare, technology, and government sectors. The ability to execute arbitrary code remotely also raises concerns about ransomware deployment or supply chain attacks if exploited in development or CI/CD environments. Organizations worldwide that integrate Spring AI into their software stacks must consider this vulnerability a critical threat to their operational security and data integrity.

Mitigation Recommendations

To mitigate CVE-2026-22738, organizations should immediately identify if their applications use the SimpleVectorStore component of Spring AI and whether user input is passed as filter expression keys. If so, upgrading to Spring AI versions 1.0.5 or later and 1.1.4 or later is essential once patches are released. Until patches are available, organizations should implement strict input validation and sanitization to prevent malicious SpEL expressions from being processed. Employing Web Application Firewalls (WAFs) with custom rules to detect and block suspicious SpEL injection patterns can provide temporary protection. Additionally, restricting network access to the affected services and monitoring logs for anomalous expression evaluations or unexpected system commands can help detect exploitation attempts. Developers should avoid using user-supplied data directly in SpEL expressions and consider alternative filtering mechanisms that do not evaluate expressions dynamically. Regularly reviewing and updating dependencies and maintaining a robust patch management process will reduce exposure to similar vulnerabilities in the future.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
vmware
Date Reserved
2026-01-09T06:54:49.675Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69c615c93c064ed76f536685

Added to database: 3/27/2026, 5:29:45 AM

Last enriched: 3/27/2026, 5:44:50 AM

Last updated: 3/27/2026, 6:42:42 AM

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses