CVE-2026-92284

Deferred Deferred - Pending Action

Memory Exhaustion via Unbounded Request Body in Caddy

Publication date: 2026-09-23

Last updated on: 2026-09-30

Assigner: GitHub, Inc.

Description

Caddy is an extensible server platform that uses TLS by default. In version 2.11.3 and earlier, in modules/caddyhttp/replacer.go, resolving http.request.body reads the complete request body with an unbounded io.Copy before request-body middleware limits apply, allowing memory exhaustion and process termination.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-23

Last Modified

2026-09-30

Generated

2026-10-14

AI Q&A

2026-09-23

EPSS Evaluated

2026-10-12

NVD

CVE-2026-92284

EUVD

EUVD-2026-85514

Affected Vendors & Products

Vendor	Product	Version / Range
caddy_project	caddy	to 2.11.4 (exc)
caddyserver	caddy	2.11.3

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-770	The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

Attack-Flow Graph

Executive Summary

CVE-2026-92284 is a memory exhaustion vulnerability in Caddy server versions 2.11.3 and earlier. It occurs in the HTTP request body handling where the server reads the entire request body without limits before middleware can restrict it. This allows attackers to send large requests causing memory exhaustion and potential process termination.

Detection Guidance

To detect this vulnerability, monitor Caddy server logs for unusually high memory usage or process terminations during request handling. Check for requests containing {http.request.body} placeholders in rewrite rules. Use system monitoring tools like 'top' or 'htop' to observe memory consumption spikes when processing large request bodies.

Impact Analysis

This vulnerability can lead to denial-of-service conditions where the Caddy server crashes due to excessive memory usage. It may disrupt services relying on the server, cause downtime, and require manual intervention to restart the process.

Compliance Impact

The vulnerability allows memory exhaustion and process termination by reading the entire request body without size limits, which could lead to denial-of-service conditions. This may impact compliance with GDPR or HIPAA by disrupting availability of systems handling sensitive data, potentially violating requirements for reliable access to personal or health information.

Mitigation Strategies

Upgrade Caddy to version 2.11.4 or later to address the memory exhaustion issue in http.request.body handling.

Hi! I’m here to help you understand CVE-2026-92284. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70