All reports
Critical

UBUNTU-CVE-2026-78663

Affected versions

Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<1.22.2-2~22.04.4
Fixed version
1.22.2-2~22.04.4
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
<1.22.2-2ubuntu0.5
Fixed version
1.22.2-2ubuntu0.5
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported
Affected versions
*
Fixed version
Not reported

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.

Links