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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

EPSS

• CVE-2025-29914: 0.32% estimated exploitation activity in the next 30 days; percentile 24.88 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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.

Published by the source

20 Mar 2025, 18:48 UTC

Last modified by the source

20 Mar 2025, 18:48 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-q9f5-625g-xm39

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-29914

Advisory: OWASP Coraza WAF has parser confusion which leads to wrong URI in `REQUEST_FILENAME`
IDs: CVE-2025-29914, GHSA-q9f5-625g-xm39
Record: https://patchnext.com/advisories/cve-2025-29914 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/corazawaf/coraza/v3 3.3.3; github.com/jptosso/coraza-waf 3.3.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/corazawaf/coraza/v3: affected < 3.3.3; fixed in 3.3.3
- Go github.com/jptosso/coraza-waf: affected < 3.3.3; fixed in 3.3.3

## Suggested inspection (read-only)
- Go github.com/corazawaf/coraza/v3: check the installed version with your package manager.
- Go github.com/jptosso/coraza-waf: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/corazawaf/coraza/v3, github.com/jptosso/coraza-waf.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-q9f5-625g-xm39 (GitHub-reviewed advisory GHSA-q9f5-625g-xm39 lists affected ranges: Go github.com/jptosso/coraza-waf >=0 =0 <3.3.3)

Commands are suggestions: review each one before running it.