← Back to search

CVE-2026-78663

9.1 CRITICAL

Published 2026-10-08 · Updated 2026-10-09

AI risk analysis

Summary
A HTTP/2 server incorrectly refunds connection-level flow control twice for the same data, allowing a malicious client to bypass configured connection-level flow control limits. This creates a potential for resource exhaustion and denial of service.
Exploitability
Exploitation requires a malicious client capable of managing HTTP/2 streams and resetting them, with no other preconditions needed beyond standard HTTP/2 support.
Blast radius
If exploited, this flaw could allow an attacker to overwhelm server resources through excessive buffering, potentially leading to service disruption or denial of service across affected connections.
Detection
No reliable host or network indicator is derivable from the published description.
Prioritized remediation
Upgrade to version 2.590 or later to fix the double refund issue in HTTP/2 flow control implementation.
http2flow-controldenial-of-service

Analysis generated locally by garnet-coder (no data left the box). AI-assisted — verify against primary sources before acting.

NVD description

The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Weaknesses

CWE-675

All references

Source data: NVD (nvd.nist.gov), public domain. Exploit-DB.ai adds local AI analysis for defensive use only.

Related CVEs

Related by shared AI tags and CWE weakness class. Browse the full archive.