CVE-2026-107835: CWE-436: Interpretation Conflict in corazawaf coraza
Description
OWASP Coraza WAF is a golang modsecurity compatible web application firewall library. Prior to 3.8.1, internal/cookies.ParseCookies in internal/cookies/cookies.go handles boundary ASCII control characters and control-only or empty cookie names differently from several backend cookie parsers. An unauthenticated attacker can craft a Cookie header so Coraza indexes or drops a cookie under a different name or value from the backend application, causing rules targeting REQUEST_COOKIES or REQUEST_COOKIES_NAMES to miss application-visible attacker data. Exploitation depends on the backend parser and affected rule scope, and interior control characters with inconsistent backend behavior are outside this advisory's remediation. This issue is fixed in version 3.8.1.
CVSS v3.1
Score 4.0medium
Affected software
corazawaf
coraza
pkg:golang/github.com/corazawaf/corazaRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OWASP Coraza WAF, a golang modsecurity-compatible web application firewall library, contains a vulnerability in its internal cookie parsing logic prior to version 3.8.1. The function internal/cookies.ParseCookies handles boundary ASCII control characters and control-only or empty cookie names differently compared to several backend cookie parsers. This discrepancy allows an unauthenticated attacker to craft a Cookie header that causes Coraza to index or drop cookies under different names or values than the backend application sees. As a result, security rules targeting REQUEST_COOKIES or REQUEST_COOKIES_NAMES may fail to detect attacker-controlled cookie data. The exploitability depends on the backend parser behavior and the scope of affected rules. The issue is resolved in Coraza version 3.8.1.
Potential Impact
An attacker can bypass certain Coraza WAF rules that inspect cookies by exploiting differences in cookie parsing between Coraza and the backend application. This may lead to attacker-controlled cookie data not being detected or blocked by the WAF, potentially allowing malicious requests to reach the backend. There is no impact on confidentiality or availability, and exploitation requires crafting specific Cookie headers. The vulnerability does not affect integrity of data but can reduce the effectiveness of the WAF's cookie-based protections.
Mitigation Recommendations
Upgrade Coraza WAF to version 3.8.1 or later, where this issue is fixed. No other mitigation is indicated by the vendor advisory. Patch status is confirmed fixed in version 3.8.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-10-08T22:34:49.289Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ac92c962cdf04f65675296b
Added to database: 10/09/2026, 18:04:06 UTC
Last enriched: 10/09/2026, 18:18:37 UTC
Last updated: 10/09/2026, 18:57:31 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.