Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/jptosso/coraza-waf

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.4GoPublished

    OWASP Coraza WAF has parser confusion which leads to wrong URI in REQUEST_FILENAME

    CVE-2025-29914 · GHSA-q9f5-625g-xm39

    Affected
    • Go github.com/jptosso/coraza-waf < 3.3.3
    Fixed in
    3.3.3· Vendor fix available
    Issue
    URLs starting with // are not parsed properly, and the request REQUESTFILENAME variable contains a wrong value, leading to potential rules bypass. Details If a request is made on an URI starting with //, coraza will set a wrong value in REQUESTFILENAME. For example, if the URI //bar/uploads/foo.php?a=b is passed to coraza: , REQUESTFILENAME will be set to /uploads/foo.php. The root cause is the usage of url.Parse to parse the URI in ProcessURI. url.Parse can parse both absolute URLs (starting with a scheme) or relative ones (just the path). //bar/uploads/foo.php is a valid absolute URI (the scheme is empty), url.Parse will consider bar as the host and the path will be set to /uploads/foo.php. PoC Impact Potential bypass of rules using REQUESTFILENAME.

    Recommended action: Upgrade to 3.3.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →