<?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/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Coraza WAF (&lt; 3.8.1) - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/products/coraza-waf--3.8.1/</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>Fri, 23 Oct 2026 01:19:09 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/products/coraza-waf--3.8.1/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Coraza WAF: Multipart upload filename parsing bypass (CVE-2026-114101)</title><link>https://feed.craftedsignal.io/briefs/2026-10-coraza-waf-bypass/</link><pubDate>Fri, 23 Oct 2026 01:19:09 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-coraza-waf-bypass/</guid><description>Coraza WAF versions prior to 3.8.1 contain a filename parsing vulnerability that allows attackers to bypass file-based security rules using specifically crafted multipart upload parameters.</description><content:encoded><![CDATA[<p>Coraza WAF versions before 3.8.1 contain a vulnerability (CVE-2026-114101) in the multipart upload filename parsing logic. The underlying use of Go's <code>mime.ParseMediaType</code> function causes the parser to ignore RFC 5987 <code>filename*</code> parameters that utilize non-UTF-8 or non-US-ASCII character sets. An attacker can leverage this behavior by providing a decoy filename parameter while utilizing an unsupported character set encoding (e.g., <code>iso-8859-1</code>) to bypass security rules configured to inspect file types or names, allowing malicious files to reach the backend application.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows for the bypass of WAF file-based security rules. This enables an attacker to upload potentially malicious files that would otherwise be blocked by the WAF, increasing the risk of remote code execution or unauthorized file access on the backend application.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Coraza to version 3.8.1 or later by updating the dependency in <code>go.mod</code>.</li>
<li>Audit existing WAF rules that rely on <code>FILES</code> or filename-based inspection to determine if they are susceptible to bypasses using non-standard character set encodings.</li>
<li>Implement additional file validation logic on the backend application server as a secondary defense layer, independent of WAF inspection.</li>
</ul>
]]></content:encoded><category domain="severity">low</category><category domain="type">advisory</category><category>vulnerability</category><category>waf</category><category>web-application</category><category>bypass</category></item></channel></rss>