Vulnerability in github.com/corazawaf/coraza/v3 (CVE-2026-107826)
Summary
Vulnerability in github.com/corazawaf/coraza/v3 (CVE-2026-107826). Risk of unauthorized operations or information disclosure. Exploitable via SecRequestBodyLimit. Mitigation: upgrade to 3.8.1 or later.
Original description
The description as published by the source.
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:
json := gjson.Parse(s)
...
truncated, err = readItems(json, key, maxRecursion, argumentLimit, byteBudget, &usedBytes, &argCount, res)
if err != nil {
return res, truncated, err
}
if !gjson.Valid(s) {
return res, truncated, errors.New("invalid JSON")
}
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):
func readItems(json gjson.Result, objKey []byte, maxRecursion int, argumentLimit int, byteBudget int, usedBytes *int, argCount *int, res map[string][]string) (truncated bool, err error) {
if byteBudget > 0 && *usedBytes >= byteBudget {
return true, nil // <-- checked first
}
if argumentLimit > 0 && *argCount >= argumentLimit {
return true, nil // <-- checked second
}
...
if maxRecursion <= 0 {
return false, errors.New("max recursion reached while…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-107826 has been found in github.com/corazawaf/coraza/v3.
Attackers can target a specific entry point like SecRequestBodyLimit over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade github.com/corazawaf/coraza/v3 to 3.8.1 or later.
If unsure, ask your IT team or search "github.com/corazawaf/coraza/v3 CVE-2026-107826" on the vendor's site.
CVE-2026-107826 (github.com/corazawaf/coraza/v3) — CWE-674 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: SecRequestBodyLimit / SecArgumentsLimit / readJSON / readItems
Patched: 3.8.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-674) exists in github.com/corazawaf/coraza/v3. Attackers reach the vulnerable code path via SecRequestBodyLimit without authentication.
Check the vendor advisory for the affected versions of github.com/corazawaf/coraza/v3. Attack surface: SecRequestBodyLimit / SecArgumentsLimit / readJSON / readItems.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 3.8.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/corazawaf/coraza/v3' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/corazawaf/coraza/v3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/corazawaf/coraza/v3を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/corazawaf/coraza/v3 to 3.8.1ステージング環境で 3.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。