Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-5gj4-9gm7-2fx2

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

CVSS 6.9 MediumEPSS 0.0029 · 22nd percentile

Published by the GitHub Advisory Database at 8 Oct 2026, 17:45 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/corazawaf/coraza/v3Go>=3.0.0, <3.8.13.8.1
Identifiers
GHSA-5gj4-9gm7-2fx2 · CVE-2026-114099 · GO-2026-6692
Weakness (CWE)
CWE-20 · CWE-436
Tags
Published
8 Oct 2026
Updated
21 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

GHSA-5gj4-9gm7-2fx2: Coraza (github.com/corazawaf/coraza/v3) versions 3.0.0 up to but not including 3.8.1 can have nested JSON values hidden from OWASP CRS inspection. An unauthenticated attacker sends a body with a nested property and a later top-level property whose literal dotted name collides with the flattened path, so the malicious value is overwritten and never inspected while backends still receive it. Upgrade to version 3.8.1 or later, which is listed as the fixed version.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.9 Medium 4.0 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 CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0029, the 22nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:11 UTC First seen by agentprime
  2. 31 Oct 2026, 14:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.