Live › vulnerability › CVE-2026-104774
Go to dashboardCoraza, a Go web application firewall library, mishandles JavaScript octal escapes in its t:jsDecode transform, decoding them into null bytes. An unauthenticated attacker can hide XSS or SQL injection payloads in octal escapes so the WAF rules miss them while the backend still decodes the attack.
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.0.0, < 3.8.0 | 3.8.0 |
3.0.0 and < 3.8.0Upgrade 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.0.0 until 3.8.0, the t:jsDecode transformation in internal/transformations/js_decode.go:64-70 includes the backslash in the octal buffer, causing ParseInt to fail and return a null byte. The flaw is triggered when a rule relies on t:jsDecode and the request contains JavaScript octal escape sequences. An unauthenticated attacker can encode attack syntax with JavaScript octal escapes so the backend decodes the intended bytes while Coraza rules using t:jsDecode inspect corrupted null-byte output. The mismatch can bypass WAF rules and expose the protected application to attacks such as cross-site scripting or SQL injection. This issue is fixed in version 3.8.0.
This page as .md · .json · in your agent: get_signal("CVE-2026-104774")
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.