Skip to main content
VulnerabilityPublished

CVE-2026-107835: corazawaf coraza · Interpretation Conflict

Affects corazawaf corazaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.0 Medium : upgrade to 3.8.1 when convenient.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
4.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.8.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade coraza and github.com/corazawaf/coraza to 3.8.1.

Affected software

ProductAffectedFixed in
corazawafcorazaAffected
  • <3.8.1
Fixed in
  • 3.8.1
Gogithub.com/corazawaf/corazapkg:golang/github.com/corazawaf/corazaOther threatsAffected
  • <3.8.1
Fixed in
  • 3.8.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…