Skip to content
Fencer Intel
medium 5.4

CVE-2025-29914 json

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

published last yr. modified 4mo ago also EUVD-2025-7160 , GHSA-q9f5-625g-xm39 , GO-2025-3537

cvss
5.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 25%
public exploits
0
none known

Summary

OWASP Coraza WAF is a golang modsecurity compatible web application firewall library. Prior to 3.3.3, if a request is made on an URI starting with //, coraza will set a wrong value in REQUEST_FILENAME. For example, if the URI //bar/uploads/foo.php?a=b is passed to coraza: , REQUEST_FILENAME will be set to /uploads/foo.php. This can lead to a rules bypass. This vulnerability is fixed in 3.3.3.

Patch / fix

  • go github.com/jptosso/coraza-waf 3.3.3
  • go github.com/corazawaf/coraza/v3 3.3.3
  • coraza coraza 3.3.3
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250327T184518-1.1

opensuse advisories openSUSE-SU-2025:14937-1

Is CVE-2025-29914 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/jptosso/coraza-waf
<3.3.3
all versions
3.3.3
go github.com/corazawaf/coraza/v3
<3.3.3
3.3.3
go github.com/corazawaf/coraza
all versions
no fix listed
go github.com/corazawaf/coraza/v2
all versions
no fix listed

Affected products

  • corazawaf coraza

Classification

Weakness
  • CWE-706 Use of Incorrectly-Resolved Name or Reference

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.