CVE-2026-114099 json
Coraza 3.0.0 before 3.8.1 WAF Bypass via JSON Key Collision
published last mo. modified 12d ago also EUVD-2026-106902 , GHSA-5gj4-9gm7-2fx2 , GO-2026-6692
- cvss
- 5.8
- 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 22%
- public exploits
- 0
- none known
Summary
Coraza from 3.0.0 before 3.8.1 has a JSON body processor that flattens nested properties into dot-separated ARGS_POST names without escaping literal dots, so distinct properties collide. Unauthenticated attackers can add a later dotted property such as account.role that overwrites a malicious nested value, hiding SQL injection payloads from OWASP CRS rules while backends still receive them.
Patch / fix
- go github.com/corazawaf/coraza/v3 3.8.1
- corazawaf coraza 3.8.1
Is CVE-2026-114099 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 FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 12d ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/corazawaf/coraza/security/advisories/GHSA-5gj4-9gm7-2fx2 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N |
| CNA | 3.1 | 5.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N |
| GitHub | 3.1 | 5.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/corazawaf/coraza/v3 | >=3.0.0, <3.8.1 |
3.8.1 |
| 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
References
-
github.com
/corazawaf/coraza/commit/52af139cab5ad10c5cb0152a161063b523907bdf
web, patch
-
github.com
/corazawaf/coraza/commit/5f577a548aeb9ca836122df4258f93ef6cfab38a
web, patch
-
github.com
/corazawaf/coraza/commit/cae3c7407e7b84372c207033de03f15f89bf351a
web, patch
-
github.com
/corazawaf/coraza/security/advisories/GHSA-5gj4-9gm7-2fx2
vendor-advisory, exploit, web, advisory
-
vulncheck.com
/advisories/coraza-3.0.0-before-3.8.1-waf-bypass-via-json-key-collision
third-party-advisory
-
github.com
/corazawaf/coraza
package
-
github.com
/corazawaf/coraza/releases/tag/v3.8.1
web
Sources
- CVE List CVE-2026-114099
- GitHub Advisory GHSA-5gj4-9gm7-2fx2
- NVD CVE-2026-114099
- OSV GO-2026-6692
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.