CVE-2026-107826 corazawaf CVE debrief

Who should care

Defenders responsible for OWASP Coraza WAF deployments should assess exposure and prioritize patching or upgrading to version 3.8.1 or later to prevent potential process crashes. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review and update configurations to ensure SecArgumentsLimit and byte budget are properly set.

Why it matters

Defenders should prioritize patching or upgrading to version 3.8.1 or later to prevent potential process crashes caused by the vulnerability in OWASP Coraza WAF.

• Potential process crashes due to unbounded-depth stack overflow
• Need to verify and update configurations to ensure SecArgumentsLimit and byte budget are properly set
• Possible impact on web application availability and reliability

Technical summary

The vulnerability is caused by the readJSON function in internal/bodyprocessors/json.go, which can stop its bounded flattening walk after reaching SecArgumentsLimit or the byte budget and then call gjson.Valid on the complete raw body. An unauthenticated attacker can submit shallow values followed by an extremely deeply nested JSON tail that was not visited by the bounded walk, causing gjson.Valid to recurse without a depth bound and terminate the hosting process with an unrecoverable fatal stack overflow.

Defensive priority

Defenders should prioritize patching or upgrading to version 3.8.1 or later to prevent potential process crashes.

Recommended defensive actions

• Patch or upgrade to version 3.8.1 or later
• Review and update configurations to ensure SecArgumentsLimit and byte budget are properly set
• Monitor for potential process crashes and implement logging and alerting
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability is caused by the readJSON function in internal/bodyprocessors/json.go, which can stop its bounded flattening walk after reaching SecArgumentsLimit or the byte budget and then call gjson.Valid on the complete raw body.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.