HTTP/3 flood is a denial-of-service attack that overwhelms a target with large volumes of HTTP/3 requests. It exploits the QUIC transport used by HTTP/3, often by multiplying work at the application layer faster than the server can complete connections, parse requests, or enforce rate limits.
What HTTP/3 flood means in practice
HTTP/3 flood is an application-layer denial-of-service pattern that abuses the HTTP/3 stack itself, not just raw bandwidth. Because HTTP/3 runs over QUIC, defenders have to think about request parsing, connection handling, and transport-level cost together, especially when the attack turns a relatively small amount of traffic into much larger server-side work.
That matters because the bottleneck is often not the network link alone. A target may still be overwhelmed if each request consumes CPU, memory, state, or log-processing capacity faster than the service can recover.
Why HTTP/3 is a useful flood target
HTTP/3 changes how servers accept and manage traffic, and that gives attackers new places to create expensive work. QUIC relies on UDP, encrypted transport behaviour, and connection state that can be stressed before application logic even gets a chance to apply normal limits.
In an HTTP/3 flood, the attacker is usually trying to force the server to spend disproportionate effort on handshakes, header processing, stream handling, or request accounting. A good overview of the protocol-specific defensive issues is covered in the HTTP/2, HTTP/3 and QUIC Security Guide.
How organisations should assess exposure
Exposure starts with knowing which services actually speak HTTP/3, which edge devices terminate it, and where QUIC is allowed through firewalls or cloud front doors. The same service can look protected at the edge while still being reachable over direct UDP paths, alternate hostnames, or misconfigured origins.
It is also important to understand whether the service depends on application-layer controls, because an HTTP/3 flood can bypass assumptions built around older HTTP/1.1 or HTTP/2 handling. The broader relationship between scrubbing, WAFs, rate limits, and layer 7 flood defence is well explained in DDoS Protection vs WAF.
Mitigation and recovery when the flood is underway
Defence usually means reducing the work factor per request and limiting the attacker's ability to scale cheaply. That can include edge rate controls, protocol-aware filtering, QUIC-specific policy, upstream scrubbing, and service-side concurrency limits that prevent one client population from consuming all request processing capacity.
If the attack is already in progress, response often becomes a layered decision about where to absorb or drop traffic, how to preserve origin capacity, and when to shift to provider-backed mitigation. A practical response pattern is described in DDoS Response Playbook, while the broader control selection trade-offs are covered in DDoS Protection Guide.
Detection, review, and post-incident hardening
Detection should look for more than traffic volume. A real HTTP/3 flood often shows up as rising request rates, unusual QUIC session churn, elevated CPU or memory use, uneven error responses, and a mismatch between ingress volume and successful application work.
After mitigation, teams should review whether the service was overrun by connection setup, header parsing, request fan-out, or logging overhead, then tighten the weakest point. The broader denial-of-service patterns that help with investigation and hunt mapping are summarised in MITRE ATT&CK T1499 Endpoint Denial of Service.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| MITRE ATT&CK | T1499 — Endpoint Denial of Service | HTTP/3 flood is a denial-of-service technique that exhausts application and service resources. |
| Recommendation — Map flood indicators to T1499 and hunt for per-layer exhaustion patterns in telemetry. | ||
| CIS Controls v8 | CIS-13 — Network Monitoring and Defense | HTTP/3 flood defence depends on monitoring, filtering and traffic-control safeguards. |
| Recommendation — Apply CIS-13 to monitor QUIC traffic and enforce defensive filtering at the edge. | ||
| NIST CSF 2.0 | PR.DS-01 — Data-at-rest is protected | Resilience against flood-driven service disruption supports protection of service data and availability. |
| DE.CM-01 — Networks and network services are monitored to find potentially adverse events | Detection of HTTP/3 flood activity depends on continuous monitoring of network and service behaviour. | |
| RS.MI-01 — Incidents are contained | Flood attacks require containment actions to limit ongoing resource exhaustion and restore service. | |
| Recommendation — Use PR.DS-01 to preserve protected service operation during traffic-exhaustion events. Use DE.CM-01 to watch for QUIC surges, request spikes and abnormal service saturation. Use RS.MI-01 to contain the attack by rate-limiting, blocking or diverting abusive traffic. | ||
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org