Quick answers
- Is CVE-2026-92284 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92284 being exploited in the wild.
- How severe is CVE-2026-92284?
- Informational severity, published 23 September 2026.
- Which products and versions are affected?
- Caddy 2.11.3 and earlier.
- Is there a fix for CVE-2026-92284?
- A patch was published on 2026-07-10: Fix available in Caddy v2.11.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-92284 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-92284?
- Check whether you run Caddy at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The {http.request.body} placeholder in modules/caddyhttp/replacer.go uses unbounded io.Copy() to buffer request bodies, bypassing the request_body middleware's size limits because placeholder resolution occurs before middleware processes the request. An attacker can trigger memory exhaustion and denial of service by sending large request bodies, potentially declaring arbitrary Content-Length headers or using chunked encoding.
Affected products
- Caddy Caddy 2.11.3 and earlier
Timeline
- 2026-07-10: disclosed: GitHub Security Advisory GHSA-j8px-rmrx-76h9 published
- 2026-07-10: patched: Fix available in Caddy v2.11.4