Vulnerability in github.com/corazawaf/coraza/v3 (CVE-2026-107833)
Summary
Vulnerability in github.com/corazawaf/coraza/v3 (CVE-2026-107833). Risk of unauthorized operations or information disclosure. Exploitable via ProcessResponse. Mitigation: upgrade to 3.8.0 or later.
Original description
The description as published by the source.
Summary
The JSON response body processor parses response bodies with no recursion
limit. ProcessResponse calls readJSON(ss, ignoreJSONRecursionLimit), and
that constant is -1. The guard in readItems only fires on == 0, so
counting down from -1 (-2, -3, ...) never reaches it. The guard is effectively
dead on the response path. The request path is fine: ProcessRequest passes the
configured limit (default 1024). There is no equivalent directive or default for
responses.
Parsing a deeply nested JSON response is CPU-bound and its cost grows
quadratically with nesting depth. A 512 KiB response (the default
ResponseBodyLimit) holds about 87,000 nesting levels and takes ~12 s to
process, keeping one core busy the whole time.
Root cause
internal/bodyprocessors/json.go
const ignoreJSONRecursionLimit = -1 // line 51
func (js *jsonBodyProcessor) ProcessResponse(reader io.Reader, v ..., _ plugintypes.BodyProcessorOptions) error {
...
data, err := readJSON(ss, ignoreJSONRecursionLimit) // line 62, passes -1
}
func (js *jsonBodyProcessor) ProcessRequest(...) error {
...
data, err := readJSON(ss, bpo.RequestBodyRecursionLimit) // line 32, default 1024
}
The guard and the decrement:
func readItems(json gjson.Result, objKey []byte, maxRecursion int, res map[string]string) error {
if maxRecursion == 0 { // line 106
return errors.New("max recursion reached while reading…
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-107833 has been found in github.com/corazawaf/coraza/v3.
Attackers can target a specific entry point like ProcessResponse over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.9/10.
What to do: upgrade github.com/corazawaf/coraza/v3 to 3.8.0 or later.
If unsure, ask your IT team or search "github.com/corazawaf/coraza/v3 CVE-2026-107833" on the vendor's site.
CVE-2026-107833 (github.com/corazawaf/coraza/v3) — CWE-674 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: ProcessResponse / readItems / ProcessRequest / ResponseBodyLimit
Patched: 3.8.0 — 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 ProcessResponse without authentication.
Check the vendor advisory for the affected versions of github.com/corazawaf/coraza/v3. Attack surface: ProcessResponse / readItems / ProcessRequest / ResponseBodyLimit.
Severity: Medium (CVSS 5.9/10). Risk of unauthorized operations or information disclosure.
Update to 3.8.0.
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.0ステージング環境で 3.8.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。