# CVE-2025-29914: OWASP Coraza WAF has parser confusion which leads to wrong URI in `REQUEST_FILENAME`

Source: https://junglewise.ai/threats/cve-2025-29914-owasp-coraza-waf-has-parser-confusion-which-leads-to-wrong-uri-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-03-25  
License: CC BY 4.0 with a link back

CVE-2025-29914 · Severity: low · CVSS 3.1 · Published 2025-03-25

OWASP Coraza WAF has parser confusion which leads to wrong URI in `REQUEST_FILENAME` in github.com/corazawaf/coraza

Technologies: [github.com/corazawaf/coraza (Go)](https://junglewise.ai/threats/technologies/github-com-corazawaf-coraza), [github.com/corazawaf/coraza/v2 (Go)](https://junglewise.ai/threats/technologies/github-com-corazawaf-coraza-v2), [github.com/corazawaf/coraza/v3 (Go)](https://junglewise.ai/threats/technologies/github-com-corazawaf-coraza-v3). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2025-29914 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-29914 being exploited in the wild.

**How severe is CVE-2025-29914?** Low severity, with a CVSS score of 3.1, published 25 March 2025.

**Which products and versions are affected?** github.com/corazawaf/coraza (Go) SEMVER:introduced=0; github.com/corazawaf/coraza/v2 (Go) SEMVER:introduced=0; github.com/corazawaf/coraza/v3 (Go) SEMVER:introduced=0,fixed=3.3.3; github.com/jptosso/coraza-waf (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=3.3.3.

**Is there a fix for CVE-2025-29914?** Yes. github.com/corazawaf/coraza/v3 (Go): upgrade to 3.3.3 or later; github.com/jptosso/coraza-waf (Go): upgrade to 3.3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-29914?** Check whether you run github.com/corazawaf/coraza (Go), github.com/corazawaf/coraza/v2 (Go), github.com/corazawaf/coraza/v3 (Go) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/corazawaf/coraza/v3 (Go): upgrade to 3.3.3 or later

  ```sh
  go get github.com/corazawaf/coraza/v3@v3.3.3
  ```

- github.com/jptosso/coraza-waf (Go): upgrade to 3.3.3 or later

  ```sh
  go get github.com/jptosso/coraza-waf@v3.3.3
  ```


## Affected products

- github.com/corazawaf/coraza (Go) SEMVER:introduced=0
- github.com/corazawaf/coraza/v2 (Go) SEMVER:introduced=0
- github.com/corazawaf/coraza/v3 (Go) SEMVER:introduced=0,fixed=3.3.3
- github.com/jptosso/coraza-waf (Go) SEMVER:introduced=0, SEMVER:introduced=0,fixed=3.3.3

## Identifiers

- CVE-2025-29914
- GHSA-q9f5-625g-xm39
- GO-2025-3537

## Related threats

- [Coraza multipart filename rule bypass via RFC 5987 charset handling](https://junglewise.ai/threats/cve-2026-114101-coraza-before-3-8-1-extracts-multipart-upload-filenames-with-go)
- [Coraza request body inspection bypass in Content-Type parsing](https://junglewise.ai/threats/cve-2026-114100-coraza-from-3-0-4-before-3-8-1-contains-a-request-body)
- [Coraza JSON body processor key collision WAF bypass](https://junglewise.ai/threats/cve-2026-114099-coraza-from-3-0-0-before-3-8-1-has-a-json-body-processor-that)
- [Coraza multipart strict validation bypass via truncated body](https://junglewise.ai/threats/cve-2026-41508-coraza-truncated-multipart-body-bypasses-multipart-strict-error)
- [Coraza CRLF injection in Native audit-log format](https://junglewise.ai/threats/cve-2026-41504-coraza-native-audit-log-format-allows-crlf-injection-and-log)