CVE-2026-78663

Double flow control refund on HTTP/2 server streams in net/http

Published Oct 8, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability occurs in Go's HTTP/2 server implementation within the net/http and golang.org/x/net/http2 packages. It incorrectly refunds flow‑control credit twice: once when a client resets a stream, and again when the request handler reads the buffered data. This double refund breaks the MaxReceiveBufferPerConnection limit, letting a malicious client send data, reset the stream, and force the server to allocate more memory than intended. The flaw is a result of improper flow‑control credit management and could enable an attacker to cause memory growth bounded only by the concurrent stream and stream‑level flow‑control limits.

Affected Systems

Any Go application that uses the standard library packages net/http, net/http/internal/http2, or the golang.org/x/net/http2 library is affected. All Go distributions containing these packages are vulnerable; specific version ranges are not yet published publicly.

Risk and Exploitability

The CVSS score of 9.1 indicates critical severity, and the EPSS score of less than 1 % suggests a very low but nonzero probability of exploitation. It is not listed in CISA’s KEV catalog. Attacks would originate from a remote HTTP/2 client that can repeatedly send data and reset to trigger the double refund, potentially leading to memory growth bounded only by the concurrent stream limit and stream‑level flow control. The repeated reset pattern is inferred from the description, as the vulnerable refund logic can be abused by a client that triggers multiple resets to bypass the connection‑level flow control. No publicly known exploit exists, and no official patch is currently available; however, the design flaw permits a modest risk of denial of service if an adversary can sustain the reset pattern.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Deploy monitoring to detect unusually high HTTP/2 stream reset rates and large buffered data usage.
  • Temporarily disable HTTP/2 on the server or limit stream concurrency until an official fix is released.
  • Reduce the MaxReceiveBufferPerConnection setting to a lower value to constrain memory allocation while monitoring for performance impact.

Generated by OpenCVE AI on October 9, 2026 at 19:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8935-1 Go vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-675
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H'}

Type Values Removed Values Added
Weaknesses CWE-399
Type Values Removed Values Added
Weaknesses CWE-770
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Go Standard Library
Go Standard Library net/http
Go Standard Library net/http2
Vendors & Products Go Standard Library
Go Standard Library net/http
Go Standard Library net/http2
Type Values Removed Values Added
Weaknesses CWE-399
Type Values Removed Values Added
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.
Title Double flow control refund on HTTP/2 server streams in net/http
References
Weaknesses
  • CWE-675

    Multiple Operations on Resource in Single-Operation Context

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
Go
Published
Updated
Oct 9, 2026, 4:42 PM
Reserved
Aug 24, 2026, 11:36 PM
Status
Awaiting Analysis
Published
Oct 8, 2026, 11:17 PM
Modified
Oct 9, 2026, 5:16 PM
Severity
Moderate
Public date
Oct 8, 2026, 10:53 PM