Read the docs
TI-2026-70115 Aliases CVE-2026-107835

Cookie parsing mismatch in OWASP Coraza WAF hides cookies from rules

Priority MEDIUM 52CWE-436Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

OWASP Coraza WAF, a Go library, is affected before 3.8.1. Its internal/cookies.ParseCookies function handles boundary control characters and control-only or empty cookie names differently from several backend cookie parsers (CWE-436). An unauthenticated remote attacker can make Coraza index or drop a cookie under a different name or value than the backend application sees, so rules targeting REQUEST_COOKIES or REQUEST_COOKIES_NAMES can miss attacker data. Exploitation depends on the backend parser and the affected rule scope.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00298 22nd percentileScored 2026-11-07
Fix Fixed coraza (corazawaf): 3.8.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
corazawafcorazabefore 3.8.13.8.1Patch availableCNA
  • coraza Vendorcorazawaf Affected before 3.8.1 Fixed in 3.8.1 Patch available CNA

Remediation

Upgrade OWASP Coraza to version 3.8.1, which fixes this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-10-29

  • Fix · CNA coraza (corazawaf) Fixed in 3.8.1

Timeline

  1. 2026-10-10 Threatist record created from CVE-2026-107835

References

Other 4

  • TI-2026-69592 Uncontrolled recursion in Coraza WAF JSON parsing crashes the process CVSS 3.1HIGH 7.5
  • TI-2026-71270 Coraza WAF silently drops arguments at ArgumentLimit, enabling rule bypass CVSS 3.1HIGH 7.2
  • TI-2026-71268 Off-by-one error in OWASP Coraza jsDecode enables WAF rule bypass CVSS 3.1MEDIUM 5.8
  • TI-2026-78712 Coraza JSON key collision lets SQL injection evade WAF rules CVSS 4.0MEDIUM 6.9
  • TI-2026-78714 Multipart filename* charset handling bypasses Coraza FILES rules CVSS 4.0MEDIUM 6.3
  • TI-2026-69596 Uncontrolled recursion in Coraza WAF JSON processing exhausts CPU CVSS 3.1MEDIUM 5.9
See all 12 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences