# Coraza: Unbounded recursion in JSON response body processor causes CPU exhaustion

Advisory record · `GHSA-3c6w-j9xm-8h2h`

- **Identifiers:** `GHSA-3c6w-j9xm-8h2h` · `CVE-2026-107833` · `GO-2026-6690`
- **State:** Confirmed
- **Severity:** CVSS 5.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-674](https://cwe.mitre.org/data/definitions/674.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 8 Oct 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

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

## Affected packages

- `github.com/corazawaf/coraza/v3` (Go): affected `>=3.0.0, <3.8.0`; fixed in `3.8.0`

## Machine-written summary

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

> Coraza (github.com/corazawaf/coraza/v3) versions 3.0.0 up to but not including 3.8.0 are affected. The JSON response body processor has no recursion limit, so a deeply nested JSON response can take roughly 12 seconds of CPU per 512 KiB body at the default settings. An attacker needs to get a backend to return such a body through the WAF, which requires response body access to be enabled. Upgrade to version 3.8.0 or later. The source gives no workaround.

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

- 5.9 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0039, the 33rd percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:11 UTC: First seen by agentprime
- 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3c6w-j9xm-8h2h)

## Sources

- [GitHub Advisory Database: GHSA-3c6w-j9xm-8h2h](https://github.com/advisories/GHSA-3c6w-j9xm-8h2h)
- [OSV: GHSA-3c6w-j9xm-8h2h](https://osv.dev/vulnerability/GHSA-3c6w-j9xm-8h2h)
- <https://github.com/corazawaf/coraza/security/advisories/GHSA-3c6w-j9xm-8h2h>
- <https://github.com/corazawaf/coraza/commit/cae3c7407e7b84372c207033de03f15f89bf351a>
- <https://github.com/corazawaf/coraza>
- <https://github.com/corazawaf/coraza/releases/tag/v3.8.0>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-3c6w-j9xm-8h2h>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-3c6w-j9xm-8h2h/>. Everything for agents: <https://agentprime.io/llms.txt>.