Jan 6, 2026·6 min read·15 visits
Coraza WAF treated URIs starting with `//` as protocol-relative URLs, interpreting the first path segment as a hostname. This caused the WAF to effectively 'delete' the first directory from the path it inspected (e.g., `//admin` became a host named `admin` with an empty path), allowing attackers to bypass Access Control Lists (ACLs) while the backend server still normalized and served the sensitive path.
A parser logic discrepancy in OWASP Coraza WAF allows attackers to bypass path-based security rules using double slashes in the URI, exploiting Go's standard URL parsing behavior.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N| Product | Affected Versions | Fixed Version |
|---|---|---|
Coraza WAF OWASP | < 3.3.3 | 3.3.3 |
| Attribute | Detail |
|---|---|
| CWE ID | CWE-706 (Incorrectly-Resolved Name) |
| Attack Vector | Network (HTTP) |
| CVSS v3.1 | 5.4 (Medium) |
| Impact | Security Bypass / ACL Evasion |
| Exploit Status | PoC Available |
| Language | Go (Golang) |
The software uses a name or reference that resolves to a resource different from the intended one, leading to incorrect authorization decisions.