withdrawn 2026-10-09 23:13Z

This entry duplicated another and was withdrawn in its favour.

Superseded by ETK-2026-1109.

ETK-2026-387Zero's internal tracking ID, independent of the CVE number.

withdrawn
no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
go:github.com/corazawaf/coraza/v3 >= 3.0.0, < 3.8.1
fixed in 3.8.1
CWE-674 Uncontrolled Recursion
ETK-2026-387, no cve assigned
pkg:golang/github.com/corazawaf/coraza/v3
11d 05h 38msince last run
–AI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Coraza versions before 3.8.1 can terminate their host process while handling certain deeply nested JSON bodies. An unauthenticated remote attacker can trigger the condition by sending JSON to an endpoint where Coraza's JSON body processor is enabled, which is normally selected for application/json requests.

mitigation

Upgrade github.com/corazawaf/coraza/v3 to version 3.8.1 or later. Until upgraded, restrict untrusted JSON requests or disable JSON body processing where operationally feasible.

fixed in 3.8.1

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

No signals recorded for this entry yet.

this entry in the feed

GET /api/v1/feed/ETK-2026-387

{
  "etk_id": "ETK-2026-387",
  "cve_id": null,
  "display_id": "ETK-2026-387",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "retired",
  "anchor_state": "awaiting_cve",
  "title": "Stack-exhaustion denial of service in Coraza JSON processing",
  "summary": "Coraza versions before 3.8.1 can terminate their host process while handling certain deeply nested JSON bodies. An unauthenticated remote attacker can trigger the condition by sending JSON to an endpoint where Coraza's JSON body processor is enabled, which is normally selected for application/json requests.",
  "mitigation": "Upgrade github.com/corazawaf/coraza/v3 to version 3.8.1 or later. Until upgraded, restrict untrusted JSON requests or disable JSON body processing where operationally feasible.",
  "vendor": "go",
  "product": "go:github.com/corazawaf/coraza/v3",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 3.0.0, < 3.8.1"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "3.8.1"
      ],
      "package_name": "github.com/corazawaf/coraza/v3",
      "purl": "pkg:golang/github.com/corazawaf/coraza/v3"
    }
  ],
  "cwes": [
    674
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": null,
  "signals": {}
}

published 2026-10-02 23:37Z
last change 2026-10-09 23:13Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.