OWASP Coraza WAF drops query parameters on URI parse failure
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 and GitHub.
Summary
OWASP Coraza WAF from 3.0.0 before 3.8.0 leaves query parameters empty when it cannot parse a request URI (CWE-20). An unauthenticated remote attacker can place control bytes in a URI passed directly by integrations such as coraza-spoa or coraza-proxy-wasm, so rules that inspect query arguments are bypassed. The bundled coraza/v3/http integration is not affected because Go net/http rejects such request targets first.
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. From 3.0.0 until 3.8.0, ProcessURI in internal/corazawaf/transaction.go handles a url.ParseRequestURI failure by retaining the raw URI but leaving QUERY_STRING, ARGS_GET, ARGS_GET_NAMES, and the GET-derived portion of ARGS empty. An unauthenticated attacker can place control bytes in a URI passed directly by integrations such as coraza-spoa, coraza-proxy-wasm, custom FFI hosts, or WASM hosts, causing Coraza to omit query parameters that the downstream integration may still process and allowing rules targeting those variables to be bypassed. The bundled coraza/v3/http integration is not affected because Go net/http rejects such malformed request targets before calling Coraza. This issue is fixed in version 3.8.0.
Why it matters now
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
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| corazawaf | coraza | 3.0.0 to before 3.8.0 | 3.8.0 | Patch available | CNA |
| — | github.com/corazawaf/coraza/v3 (Go) | 3.0.0 to before 3.8.0 | 3.8.0 | Patch available | GHSA-x26q-wvhg-fh4m |
- coraza Vendorcorazawaf Affected 3.0.0 to before 3.8.0 Fixed in 3.8.0 Patch available CNA
- github.com/corazawaf/coraza/v3 (Go) Vendor— Affected 3.0.0 to before 3.8.0 Fixed in 3.8.0 Patch available GHSA-x26q-wvhg-fh4m
Remediation
Upgrade github.com/corazawaf/coraza/v3 to version 3.8.0. The sources list no fixed version for coraza.
Written with Claude Haiku 5.5 from the sources below · 2026-10-29
- Fix · CNA coraza (corazawaf) Fixed in 3.8.0
- Fix · GHSA-x26q-wvhg-fh4m github.com/corazawaf/coraza/v3 (Go) Fixed in 3.8.0 Advisory →
Timeline
- 2026-10-08 Threatist record created from GHSA-x26q-wvhg-fh4m
- 2026-10-09 Alias added: CVE-2026-107825
- 2026-10-10 Title updated · CNA
- 2026-10-10 CVSS score added · CNA
- 2026-10-10 Weakness changed · CNA
- 2026-10-10 Affected versions changed · CNA
- 2026-10-10 3 new references · CNA
- 2026-10-14 CISA SSVC decision points changed
- 2026-10-14 Priority changed: LOW → MEDIUM
References
More corazawaf vulnerabilities
- 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
Sources
- CVE-2026-107825 · CVE Program
- CVE-2026-107825 · NVD
- FIRST EPSS
- GHSA-x26q-wvhg-fh4m · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences