<?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>Redis — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/redis/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Fri, 27 Mar 2026 06:16:38 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/redis/feed.xml" rel="self" type="application/rss+xml"/><item><title>Spring AI Redis Store TAG Injection Vulnerability (CVE-2026-22744)</title><link>https://feed.craftedsignal.io/briefs/2026-03-spring-ai-redis-injection/</link><pubDate>Fri, 27 Mar 2026 06:16:38 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-spring-ai-redis-injection/</guid><description>CVE-2026-22744 is a code injection vulnerability in Spring AI's RedisFilterExpressionConverter which allows an attacker to inject arbitrary commands into RediSearch TAG blocks via unescaped user-controlled strings, affecting versions 1.0.0 before 1.0.5 and 1.1.0 before 1.1.4.</description><content:encoded><![CDATA[<p>CVE-2026-22744 is a critical vulnerability found within the <code>RedisFilterExpressionConverter</code> of the Spring AI Redis Store. The vulnerability arises because the <code>stringValue()</code> function directly inserts user-supplied strings into the <code>@field:{VALUE}</code> RediSearch TAG block without proper sanitization or escaping. This allows an attacker to inject arbitrary commands or data into the Redis database if they can control the input used as a filter value for a TAG field. This vulnerability affects…</p>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>injection</category><category>spring-ai</category><category>redis</category></item><item><title>Multiple Vulnerabilities in Redis</title><link>https://feed.craftedsignal.io/briefs/2026-03-redis-vulns/</link><pubDate>Wed, 25 Mar 2026 10:23:30 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-redis-vulns/</guid><description>Multiple vulnerabilities in Redis allow an attacker to execute arbitrary program code and perform a denial-of-service attack.</description><content:encoded><![CDATA[<p>Multiple vulnerabilities have been identified in Redis, a popular in-memory data structure store, which could allow a remote attacker to execute arbitrary code or cause a denial-of-service (DoS) condition. The specifics of these vulnerabilities are not detailed in this advisory. While the exact exploitation methods remain unclear from the source, the potential impact on confidentiality, integrity, and availability is significant, particularly for organizations heavily reliant on Redis for critical services. This threat brief is focused on providing generic detections due to the missing specifics.</p>
<h2 id="attack-chain">Attack Chain</h2>
<p>Given the limited information, the following attack chain is a generalized hypothetical scenario:</p>
<ol>
<li>Attacker identifies a vulnerable Redis instance exposed to the network.</li>
<li>Attacker exploits a vulnerability (specific CVE details are unknown) to gain initial access. This could involve sending a specially crafted request to the Redis server.</li>
<li>Successful exploitation allows the attacker to execute arbitrary commands within the context of the Redis server.</li>
<li>Attacker leverages code execution to write malicious code to disk.</li>
<li>Attacker executes the malicious code, potentially gaining a foothold on the server.</li>
<li>Attacker uses the compromised Redis server to launch further attacks against internal network resources or to cause a denial of service. This may involve flooding the network with traffic.</li>
<li>Alternatively, the attacker may directly leverage the Redis vulnerabilities to perform a denial of service by crashing the server or exhausting its resources.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of these Redis vulnerabilities could lead to complete compromise of the affected server, potentially allowing the attacker to steal sensitive data, disrupt critical services, or gain a foothold in the internal network. Denial-of-service attacks could result in significant downtime and financial losses. The impact will vary depending on the role Redis plays within the affected organization&rsquo;s infrastructure.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Monitor Redis logs (if available) for unusual commands or activity. This can be achieved by enabling Redis logging and deploying the Sigma rule <code>Detect Suspicious Redis Commands</code> to a SIEM.</li>
<li>Implement network segmentation and access controls to limit access to Redis instances.</li>
<li>Regularly audit Redis configurations to ensure they adhere to security best practices.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>redis</category><category>vulnerability</category><category>code execution</category><category>denial of service</category></item></channel></rss>