# CVE-2026-114099: Coraza 3.0.0 before 3.8.1 WAF Bypass via JSON Key Collision


- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-5gj4-9gm7-2fx2, GHSA-vmwg-gmpq-826x, GO-2026-6692

## What is CVE-2026-114099?

CVE-2026-114099 is a medium-severity vulnerability in corazawaf coraza, published on 21 Oct 2026. 

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-114099?

5 open source packages ship an affected version, including github.com/corazawaf/coraza/v3, github.com/corazawaf/coraza and github.com/corazawaf/coraza/v2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/corazawaf/coraza/v3` | Go | From 3.0.0 | 3.8.1 |
| `github.com/corazawaf/coraza/v3` | Go | From 3.0.0 | 3.8.1 |
| `github.com/corazawaf/coraza/v3` | Go | From 3.0.0 | 3.8.1 |
| `github.com/corazawaf/coraza` | Go | All versions | None |
| `github.com/corazawaf/coraza/v2` | Go | All versions | None |

## How do I fix CVE-2026-114099?

Upgrade github.com/corazawaf/coraza/v3 to 3.8.1 or later.

## Is CVE-2026-114099 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114099 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114099 and fix it if it is affected.

What it is: CVE-2026-114099 is a medium-severity vulnerability in corazawaf coraza, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114099 exists.

Affected packages and fixed versions:
- github.com/corazawaf/coraza/v3 (Go): affected from 3.0.0; fixed in 3.8.1
- github.com/corazawaf/coraza/v3 (Go): affected from 3.0.0; fixed in 3.8.1
- github.com/corazawaf/coraza/v3 (Go): affected from 3.0.0; fixed in 3.8.1
- github.com/corazawaf/coraza (Go): affected all versions; no fix listed
- github.com/corazawaf/coraza/v2 (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114099/ (Markdown: https://insights.sbomify.com/CVE-2026-114099/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114099
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114099
- OSV: https://osv.dev/vulnerability/CVE-2026-114099

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114099/
Summaries are generated and may contain mistakes; the official description above is the record.