Live › vulnerability › CVE-2026-41508
Go to dashboardThe Coraza Go WAF library, versions 3.4.0 through 3.8.0, treats a truncated multipart body as a non-fatal parse error and does not set MULTIPART_STRICT_ERROR. An attacker can send a truncated multipart body so that the strict-error rules 200002 and 200003 never fire, letting multipart parser-disagreement payloads reach a backend that reads the body differently.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/corazawaf/coraza | go | all versions | – |
| github.com/corazawaf/coraza/v2 | go | all versions | – |
| github.com/corazawaf/coraza/v3 | go | >= 3.4.0, < 3.8.0 | 3.8.0 |
go list -m github.com/corazawaf/coraza/v3
If the reported version is >= 3.4.0 and < 3.8.0, the module is affected.
Upgrade github.com/corazawaf/coraza/v3 to 3.8.0 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
OWASP Coraza WAF is a golang modsecurity compatible web application firewall library. From 3.4.0 until 3.8.0, the multipart processor in internal/bodyprocessors/multipart.go treats io.ErrUnexpectedEOF as nonfatal without setting MULTIPART_STRICT_ERROR. A remote attacker can submit a truncated multipart body that produces io.ErrUnexpectedEOF, causing parsing to stop without raising the strict-error signal used by the recommended defensive rule. Rules 200002 and 200003 do not fire, allowing multipart parser-disagreement payloads to reach a backend that interprets the truncated body differently. This issue is fixed in version 3.8.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-41508")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.