Vulnerability · CVE-2026-114100
Coraza: URL-encoded form Content-Type parameters bypass Coraza body inspection in github.com/corazawaf/coraza
Published Oct 8, 2026 · catalog updated Oct 21, 2026 · Coraza: URL-encoded form Content-Type
Open the advisory
Exploitation likelihood is not on this record for CVE-2026-114100. A missing EPSS score is not a low risk. Compare Coraza: URL-encoded form Content-Type with the linked advisory before you change production.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Coraza: URL-encoded form Content-Type).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- Medium6.9
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Advisory link
- Affected products
- Go github.com/corazawaf/coraza · Go github.com/corazawaf/coraza/v2 · Go github.com/corazawaf/coraza/v3
### Summary Coraza fails to inspect URL-encoded form bodies when their valid contains a media-type parameter, for example: An unauthenticated attacker can use this header to hide the complete form body from custom Coraza rules that inspect or , while the bundled Go HTTP middleware forwards the body and the backend parses it normally. This is a deterministic request-body inspection bypass. Suggested severity: **Medium**. Current OWASP CRS includes rule , which forces fallback inspection and mitigates this path; this report does not claim a bypass of an unmodified current CRS ruleset ### Details The affected component is request-body processor selection in [ ](https://github.com/corazawaf/coraza/blob/db9850b2dd8992f97a8cefe08d0cb4edd966a04c/internal/corazawaf/transaction.go#L371-L390). compares the complete lowercased header value using exact equality: Source: [ , lines 383-390](https://github.com/corazawaf/coraza/blob/db9850b2dd8992f97a8cefe08d0cb4edd966a04c/internal/corazawaf/transaction.go#L383-L390). The media type of remains ; is a parameter. Because Coraza compares the entire header, the comparison fails and remains empty. treats the empty processor as success: Source: [ , lines 1115-1120](https://github.com/corazawaf/coraza/blob/db9850b2dd8992f97a8cefe08d0cb4edd966a04c/internal/corazawaf/transaction.go#L1115-L1120). Coraza therefore evaluates phase 2 without parsing the body and without setting . The [URL-encoded processor that normally populates , , and ](https://github.com/corazawaf/coraza/blob/db9850b2dd8992f97a8cefe08d0cb4edd966a04c/internal/bodyprocessors/urlencoded.go#L19-L33) is never invoked. The [bundled middleware buffers and reconstructs the full request body before invoking the backend](https://github.com/corazawaf/coraza/blob/db9850b2dd8992f97a8cefe08d0cb4edd966a04c/http/middleware.go#L69-L97). The backend consequently receives data that was absent from Coraza's body variables. The issue exists in the standard compiled implementation; no special bu
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Go github.com/corazawaf/corazaversion unspecified
- Go github.com/corazawaf/coraza/v2version unspecified
- Go github.com/corazawaf/coraza/v33.0.4 → 3.8.1
How to fix CVE-2026-114100
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for CVE-2026-114100. A missing EPSS score is not a low risk. Compare Coraza: URL-encoded form Content-Type with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with 3.0.4 → 3.8.1. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-20: Improper Input Validation; CWE-436. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Oct 19, 2026 · GitHub Advisory Database
Detected
Coraza: URL-encoded form Content-Type parameters bypass Coraza body inspection in github.com/corazawaf/coraza
Oct 21, 2026 · GitHub Advisory Database
Fix available
github.com/corazawaf/coraza/v3 fixed in 3.8.1
Oct 21, 2026 · GitHub Advisory Database
Fix available
github.com/corazawaf/coraza/v3 fixed in 3.8.1
Oct 21, 2026 · GitHub Advisory Database
Updated
Coraza: URL-encoded form Content-Type parameters bypass Coraza body inspection in github.com/corazawaf/coraza
Oct 21, 2026 · NIST NVD
Updated
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 whi
Sources
- CVE.orgVulnerability recordCVE-2026-114100
Official CVE identifier
cve.org - GitHub Advisory DatabasePackage advisoryGHSA-w253-m66g-rx24
GitHub Advisory Database record mirrored by OSV.
github.com - Go Vulnerability DatabasePackage advisoryGHSA-w253-m66g-rx24
Coraza: URL-encoded form Content-Type parameters bypass Coraza body inspection
osv.dev - Go Vulnerability DatabasePackage advisoryGO-2026-6698
Coraza: URL-encoded form Content-Type parameters bypass Coraza body inspection in github.com/corazawaf/coraza
osv.dev - NIST NVDVulnerability recordCVE-2026-114100
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 ca
nvd.nist.gov - OpenSSF OSV / OSV ScannerPackage advisoryGHSA-w253-m66g-rx24
Coraza: URL-encoded form Content-Type parameters bypass Coraza body inspection
osv.dev - OpenSSF OSV / OSV ScannerPackage advisoryGO-2026-6698
Coraza: URL-encoded form Content-Type parameters bypass Coraza body inspection in github.com/corazawaf/coraza
osv.dev
References
Freshness
Last verified in this catalog Oct 21, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.