<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Spring AI (1.0.x &lt; 1.0.6) — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/spring-ai-1.0.x--1.0.6/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 28 Apr 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/spring-ai-1.0.x--1.0.6/feed.xml" rel="self" type="application/rss+xml"/><item><title>Spring AI Vulnerabilities CVE-2026-40967 and CVE-2026-40978</title><link>https://feed.craftedsignal.io/briefs/2026-04-spring-ai-vulns/</link><pubDate>Tue, 28 Apr 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-spring-ai-vulns/</guid><description>Spring released security advisories on April 27, 2026, to address a VectorStore FilterExpression Converter injection vulnerability (CVE-2026-40967) and a SQL Injection vulnerability (CVE-2026-40978) in Spring AI versions prior to 1.0.6 and 1.1.5.</description><content:encoded><![CDATA[<p>On April 27, 2026, Spring published security advisories addressing critical vulnerabilities within the Spring AI framework. Specifically, CVE-2026-40967 details a VectorStore FilterExpression Converter injection vulnerability, while CVE-2026-40978 outlines a SQL Injection flaw within the CosmosDBVectorStore.doDelete() function. These vulnerabilities affect Spring AI versions 1.0.x prior to 1.0.6 and 1.1.x prior to 1.1.5. Exploitation of these vulnerabilities could allow for unauthorized data access or modification, potentially leading to significant data breaches and system compromise. It is crucial for organizations utilizing Spring AI to apply the necessary updates promptly to mitigate these risks.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker identifies a vulnerable Spring AI instance running a version prior to 1.0.6 or 1.1.5.</li>
<li>For CVE-2026-40967 (VectorStore FilterExpression Converter injection): the attacker crafts a malicious FilterExpression designed to inject arbitrary code during the conversion process.</li>
<li>The malicious FilterExpression is submitted to the vulnerable VectorStore component via a user-controlled input or API endpoint.</li>
<li>The VectorStore attempts to convert the FilterExpression, triggering the injection vulnerability.</li>
<li>Arbitrary code is executed within the context of the Spring AI application, potentially granting the attacker control over the system.</li>
<li>For CVE-2026-40978 (SQL Injection in CosmosDBVectorStore.doDelete()): The attacker crafts a SQL injection payload.</li>
<li>The malicious SQL payload is inserted into the <code>doDelete()</code> function via a user-controlled input or API endpoint.</li>
<li>The injected SQL code is executed against the CosmosDB database, enabling data exfiltration, modification, or deletion.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-40967 and CVE-2026-40978 can lead to significant data breaches, unauthorized access to sensitive information, and complete compromise of the Spring AI application. This can impact any sector utilizing Spring AI for AI-powered applications, including finance, healthcare, and government. The impact could range from data theft and ransomware deployment to denial of service and reputational damage.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Immediately upgrade Spring AI to version 1.0.6 or 1.1.5 or later to address CVE-2026-40967 and CVE-2026-40978.</li>
<li>Monitor web server logs (category <code>webserver</code>, product <code>linux</code>) for suspicious requests targeting Spring AI endpoints, looking for unusual FilterExpression patterns or SQL syntax, to identify potential exploitation attempts.</li>
<li>Implement input validation and sanitization measures within Spring AI applications to prevent FilterExpression injection and SQL injection attacks.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>vulnerability</category><category>sql-injection</category><category>code-injection</category><category>spring-ai</category></item></channel></rss>