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.
References
Configurations
No configuration.
History
09 Oct 2026, 17:16
| Type | Values Removed | Values Added |
|---|---|---|
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 9.1 |
| CWE | CWE-675 |
08 Oct 2026, 23:17
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-08 23:17
Updated : 2026-10-09 17:16
NVD link : CVE-2026-78663
Mitre link : CVE-2026-78663
CVE.ORG link : CVE-2026-78663
JSON object : View
Products Affected
No product.
CWE
CWE-675
Multiple Operations on Resource in Single-Operation Context
