Vulnerabilities

Vulnerability · CVE-2026-114099

Coraza body processor has a JSON key collision that allows unauthenticated attackers to bypass OWASP CRS inspection

Published Oct 8, 2026 · catalog updated Oct 21, 2026 · Coraza body processor has

Open the advisory

Exploitation likelihood is not on this record for CVE-2026-114099. A missing EPSS score is not a low risk. Compare Coraza body processor has 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 body processor has).
  • 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
Medium5.8
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's JSON body processor converts nested JSON properties into dot-separated names without escaping dots contained in literal property names. Two distinct JSON properties can therefore collapse into the same Coraza variable An unauthenticated attacker can place a malicious value in a nested property and then overwrite only Coraza's representation with a harmless dotted property: Coraza stores both properties as ; the later value replaces the SQL-injection value. Standard backend JSON parsers preserve the two distinct properties and expose the malicious nested value as . This bypasses the complete current OWASP Core Rule Set (CRS) for the hidden value. In the supplied control-pair PoC, CRS v4.25 blocks the nested SQL-injection value with rule . Adding the dotted decoy makes the same attack pass with no interruption, while Go's standard JSON parser still returns the malicious nested value. ### Details The affected component is the JSON body processor in [ ](https://github.com/corazawaf/coraza/blob/db9850b2dd8992f97a8cefe08d0cb4edd966a04c/internal/bodyprocessors/json.go#L21-L48). creates a single and begins every generated path with : Source: [ , lines 81-94](https://github.com/corazawaf/coraza/blob/db9850b2dd8992f97a8cefe08d0cb4edd966a04c/internal/bodyprocessors/json.go#L81-L94). For every object level, appends a literal dot followed by the unescaped property name: Source: [ , lines 111-120](https://github.com/corazawaf/coraza/blob/db9850b2dd8992f97a8cefe08d0cb4edd966a04c/internal/bodyprocessors/json.go#L111-L120). Scalar values are stored in the map using the resulting flattened string: Source: [ , lines 122-145](https://github.com/corazawaf/coraza/blob/db9850b2dd8992f97a8cefe08d0cb4edd966a04c/internal/bodyprocessors/json.go#L122-L145). This produces a collision: Because both values use the same Go map key, the property appearing later in the JSON document overwrites the earlier value. The malicious value no longer exists anywhere in the ordinary colle

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.0 → 3.8.1

How to fix CVE-2026-114099

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-114099. A missing EPSS score is not a low risk. Compare Coraza body processor has with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 3.0.0 → 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.

  1. Oct 8, 2026 · GitHub Advisory Database

    Detected

    ### Summary Coraza's JSON body processor converts nested JSON properties into dot-separated names without escaping dots contained in literal property names. Two distinct JSON properties can therefore collapse into the same Coraza variable An unauthenticated attacker can place a malicious value in a nested property and then overwrite only Coraza's representation with a harmless dotted property: Cor

  2. Oct 21, 2026 · GitHub Advisory Database

    Fix available

    github.com/corazawaf/coraza/v3 fixed in 3.8.1

  3. Oct 21, 2026 · GitHub Advisory Database

    Fix available

    github.com/corazawaf/coraza/v3 fixed in 3.8.1

  4. Oct 21, 2026 · GitHub Advisory Database

    Updated

    ### Summary Coraza's JSON body processor converts nested JSON properties into dot-separated names without escaping dots contained in literal property names. Two distinct JSON properties can therefore collapse into the same Coraza variable An unauthenticated attacker can place a malicious value in a nested property and then overwrite only Coraza's representation with a harmless dotted property: Cor

Sources

  • CVE.orgVulnerability recordCVE-2026-114099

    Official CVE identifier

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-5gj4-9gm7-2fx2

    GitHub Advisory Database record mirrored by OSV.

    github.com
  • Go Vulnerability DatabasePackage advisoryGHSA-5gj4-9gm7-2fx2

    Coraza body processor has a JSON key collision that allows unauthenticated attackers to bypass OWASP CRS inspection

    osv.dev
  • Go Vulnerability DatabasePackage advisoryGO-2026-6692

    Coraza body processor has a JSON key collision that allows unauthenticated attackers to bypass OWASP CRS inspection in github.com/corazawaf/coraza

    osv.dev
  • OpenSSF OSV / OSV ScannerPackage advisoryGHSA-5gj4-9gm7-2fx2

    Coraza body processor has a JSON key collision that allows unauthenticated attackers to bypass OWASP CRS inspection

    osv.dev
  • OpenSSF OSV / OSV ScannerPackage advisoryGO-2026-6692

    Coraza body processor has a JSON key collision that allows unauthenticated attackers to bypass OWASP CRS 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.

CVE-2026-114099: Coraza body processor has a JSON key collision tha… · ZeroDay Findings