Skip to content

HTTP/2 DDoS vulnerability

Moderate
trowski published GHSA-8grv-jq2g-cfhw Feb 8, 2026

Package

composer amphp/http-server (Composer)

Affected versions

>= 3.0.0-beta.1
>= 2.0.0-rc1

Patched versions

3.4.4
2.1.10

Description

Versions of amphp/http-server prior to 3.4.4 for the 3.x release branch and prior to 2.1.10 for the 2.x release branch are vulnerable to the HTTP/2 "MadeYouReset" DoS attack described by CVE-2025-8671 and https://kb.cert.org/vuls/id/767506.

In versions 3.4.4 and 2.1.10, stream reset protection has been refactored to account for the number of reset streams within a sliding time window.

Note that your application must expose HTTP/2 connections directly to be affected by this vulnerability. Servers behind a proxy using HTTP/1.x such as nginx are not affected.


Original security advisory

Dear amphp Security Team,

We are writing to responsibly disclose a newly identified vulnerability in HTTP/2 with severe DDoS effects. This vulnerability introduces a novel method of exploitation against HTTP/2 server implementations — including the latest version of amphp http-server.

This vulnerability affects recent versions of several major servers and implementations, as this is a logical protocol-level vulnerability, not a flaw in a specific implementation.

We are security researchers from Tel Aviv University working on the resilience of Internet protocols. Our team has prior experience discovering logical vulnerabilities in core internet protocols, several of which have received CVEs.

We are committed to following a coordinated disclosure process and ensuring that vendors have sufficient time to patch before any public presentation or publication.

Disclosure & Coordination Timeline

We propose a standard embargo period of three months, during which no party shall publicly disclose the vulnerability details or release a patch. Concurrently, we are preparing an academic paper for submission to a top security conference, in alignment with the embargo period.

Next Steps

As this vulnerability affects multiple vendors and could have a wide impact, we suggest establishing a secure channel for sharing further details.

Upon confirmation of the embargo process, we will provide full technical details and a proof of concept code.

Best regards,

Gal Bar Nahum, Anat Bremler-Barr, Yaniv Harel

Tel Aviv University

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CVE ID

CVE-2025-8671

Weaknesses

No CWEs

Credits