Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

Coraza JSON body processor: argument-limit truncation reopens an unbounded-depth gjson.Valid stack overflow (process crash)

CVE-2026-107826GHSA-6gcq-wc29-5xf2

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • 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
    Fixed in
    no fixed version recorded

  • Go github.com/corazawaf/coraza/v2

    Affected
    every version
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
  • CVE-2026-107826: 0.46% estimated exploitation activity in the next 30 days; percentile 40.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The JSON body processor (internal/bodyprocessors/json.go) can be made to crash the whole process with an unrecoverable fatal error: stack overflow, using a request body that is well under the recommended SecRequestBodyLimit and the default SecArgumentsLimit. Root cause readJSON (json.go:113-143) runs a bounded, best-effort flattening walk (readItems) and afterwards calls gjson.Valid(s) on the raw body if readItems returned no error: gjson.Valid (gjson v1.18.0, validany - validarray/validobject) recurses once per nesting level with no depth bound. readItems does have a depth bound (maxRecursion), enforced here (json.go:163-182): The byte-budget and argument-limit checks run before the recursion-depth check, and they short-circuit the walk with truncated=true, err=nil instead of recursing further. If the configured SecArgumentsLimit (ArgumentLimit, default 1000, internal/corazawaf/waf.go:359) is reached by earlier, shallow values in the document, readItems stops walking before…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-6gcq-wc29-5xf2

  2. Revision 2 · amended ·

    Amended from osv record GO-2026-6693

  3. Revision 1 · created ·

    Published from osv record GHSA-6gcq-wc29-5xf2

Agent brief

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

# Patch Next advisory brief: CVE-2026-107826

Advisory: Coraza JSON body processor: argument-limit truncation reopens an unbounded-depth gjson.Valid stack overflow (process crash)
IDs: CVE-2026-107826, GHSA-6gcq-wc29-5xf2
Record: https://patchnext.com/advisories/cve-2026-107826 (revision 3, source checked 26 Oct 2026, 15:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
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-6693 (OSV record GO-2026-6693 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-6gcq-wc29-5xf2 (OSV record GHSA-6gcq-wc29-5xf2 lists affected ranges: Go github.com/corazawaf/coraza/v3 >=3.0.0 <3.8.1 (fixed))
- Verified: https://github.com/advisories/GHSA-6gcq-wc29-5xf2 (GitHub-reviewed advisory GHSA-6gcq-wc29-5xf2 lists affected ranges: Go github.com/corazawaf/coraza/v3 >=3.0.0 <3.8.1)

Commands are suggestions: review each one before running it.

Loading voting…