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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N

EPSS

• CVE-2026-114099: 0.29% estimated exploitation activity in the next 30 days; percentile 22.01 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Coraza's JSON body processor converts nested JSON properties into dot-separated ARGSPOST 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 ARGSPOST:json.account.role; the later value safe replaces the SQL-injection value. Standard backend JSON parsers preserve the two distinct properties and expose the malicious nested value as account.role. 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 949110. 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…

Published by the source

8 Oct 2026, 17:45 UTC

Last modified by the source

21 Oct 2026, 10:57 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5gj4-9gm7-2fx2

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6692

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-5gj4-9gm7-2fx2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-114099

Advisory: Coraza body processor has a JSON key collision that allows unauthenticated attackers to bypass OWASP CRS inspection
IDs: CVE-2026-114099, GHSA-5gj4-9gm7-2fx2
Record: https://patchnext.com/advisories/cve-2026-114099 (revision 3, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/corazawaf/coraza/v3 3.8.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/corazawaf/coraza/v3: affected >= 3.0.0, < 3.8.1; fixed in 3.8.1
- Go github.com/corazawaf/coraza: affected every version
- Go github.com/corazawaf/coraza/v2: affected every version

## Suggested inspection (read-only)
- Go github.com/corazawaf/coraza/v3: check the installed version with your package manager.
- Go github.com/corazawaf/coraza: check the installed version with your package manager.
- Go github.com/corazawaf/coraza/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/corazawaf/coraza/v3, github.com/corazawaf/coraza, github.com/corazawaf/coraza/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6692 (OSV record GO-2026-6692 lists affected ranges: Go github.com/corazawaf/coraza >=0; Go github.com/corazawaf/coraza/v2 >=0; Go github.com/corazawaf/coraza/v3 >=3.0.0 <3.8.1 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-5gj4-9gm7-2fx2 (OSV record GHSA-5gj4-9gm7-2fx2 lists affected ranges: Go github.com/corazawaf/coraza/v3 >=3.0.0 <3.8.1 (fixed))
- Verified: https://github.com/advisories/GHSA-5gj4-9gm7-2fx2 (GitHub-reviewed advisory GHSA-5gj4-9gm7-2fx2 lists affected ranges: Go github.com/corazawaf/coraza/v3 >=3.0.0 <3.8.1)

Commands are suggestions: review each one before running it.