# CVE-2026-114100: Coraza from 3.0.4 before 3.8.1 Request Body Inspection Bypass via Content-Type


- **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:** 21 Oct 2026
- **Also known as:** GHSA-5846-6v99-476c, GHSA-w253-m66g-rx24, GO-2026-6698

## What is CVE-2026-114100?

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

### Official description

Coraza from 3.0.4 before 3.8.1 contains a request body inspection bypass because request-body processor selection compares the entire Content-Type value exactly, so URL-encoded bodies whose Content-Type carries a media-type parameter are never parsed. Unauthenticated attackers can send application/x-www-form-urlencoded; charset=UTF-8 to keep ARGS_POST and REQUEST_BODY empty, evading body rules while the backend still processes the payload.

Weakness: CWE-20 (Improper Input Validation)

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

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.4 | 3.8.1 |
| `github.com/corazawaf/coraza/v3` | Go | From 3.0.4 | 3.8.1 |
| `github.com/corazawaf/coraza/v3` | Go | From 3.0.4 | 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-114100?

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

## Is CVE-2026-114100 being exploited?

There is no known exploitation of CVE-2026-114100 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114100 is a medium-severity vulnerability in corazawaf coraza, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114100 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/corazawaf/coraza/v3 (Go): affected from 3.0.4; fixed in 3.8.1
- github.com/corazawaf/coraza/v3 (Go): affected from 3.0.4; fixed in 3.8.1
- github.com/corazawaf/coraza/v3 (Go): affected from 3.0.4; 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-114100/ (Markdown: https://insights.sbomify.com/CVE-2026-114100/index.md)
```

## Sources

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

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