CVE-2025-8671

A mismatch caused by client-triggered server-sent stream resets between HTTP/2 specifications and the internal architectures of some HTTP/2 implementations may result in excessive server resource consumption leading to denial-of-service (DoS). By opening streams and then rapidly triggering the server to reset them—using malformed frames or flow control errors—an attacker can exploit incorrect stream accounting. Streams reset by the server are considered closed at the protocol level, even though backend processing continues. This allows a client to cause the server to handle an unbounded number of concurrent streams on a single connection. This CVE will be updated as affected product details are released.

A mismatch caused by client-triggered server-sent stream resets between HTTP/2 specifications and the internal architectures of some HTTP/2 implementations may result in excessive server resource consumption leading to denial-of-service (DoS). By opening streams and then rapidly triggering the server to reset them—using malformed frames or flow control errors—an attacker can exploit incorrect stream accounting. Streams reset by the server are considered closed at the protocol level, even though backend processing continues. This allows a client to cause the server to handle an unbounded number of concurrent streams on a single connection. This CVE will be updated as affected product details are released.

Pingora deployments using versions prior to 0.6.0 that include HTTP/2 server support may be affected by the vulnerability described in CVE-2025-8671. Under certain conditions, Pingora applications may allocate buffers before the HTTP/2 reset and resulting stream cancellation is processed by the server. Repeated resets can force excessive memory consumption and lead to denial-of-service. On affected versions, malicious clients could trigger unusually high memory consumption, which may result in service instability or process termination. This issue is addressed by ensuring Pingora uses patched versions of HTTP/2 dependencies that include reset-handling safeguards to release connection resources before excessive memory buildup. Users are requested to upgrade to versions >= 0.6.0, which incorporates the required fixes.

Una discrepancia causada por el restablecimiento de flujos enviados por el servidor, activados por el cliente, entre las especificaciones HTTP/2 y las arquitecturas internas de algunas implementaciones de HTTP/2 puede resultar en un consumo excesivo de recursos del servidor, lo que resulta en una denegación de servicio (DoS). Al abrir flujos y luego activar rápidamente el servidor para que los restablezca (mediante tramas malformadas o errores de control de flujo), un atacante puede explotar la contabilidad incorrecta de los flujos. Los flujos restablecidos por el servidor se consideran cerrados a nivel de protocolo, aunque el procesamiento del backend continúe. Esto permite que un cliente haga que el servidor gestione un número ilimitado de flujos simultáneos en una sola conexión. Esta CVE se actualizará a medida que se publiquen los detalles de los productos afectados.