CVE-2026-56816

Netty: Memory Exhaustion via HTTP/3 Reserved Frame Types

Published Jul 21, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
Netty is a network application framework for development of protocol servers and clients. Prior to 4.2.16.Final, Netty's `Http3FrameCodec` buffers incoming data for HTTP/3 reserved frame types up to the wire-specified payload length without limits; `decodeFrame` trusts `payLoadLength`, allowing an attacker to open multiple QUIC streams and send reserved frames with very large payload lengths to cause memory exhaustion and denial of service. This issue is fixed in version 4.2.16.Final.

Analysis

AI-generated

Technical impact

The vulnerability resides in Netty’s Http3FrameCodec, where incoming data for HTTP/3 reserved frame types are buffered up to the wire‑specified payload length without any server‑side limit. Because the decoder trusts the payload length field, an attacker can open multiple QUIC streams and send reserved frames with extremely large lengths, exhausting heap space and causing the application to fail. This is a classic memory exhaustion flaw that can lead to sustained denial of service for the affected process.

Affected Systems

The issue affects the Netty network application framework, versions prior to 4.2.16.Final. Clients and servers that use these earlier Netty releases are vulnerable; any deployment of Netty for HTTP/3 traffic is impacted until the update is applied.

Risk and Exploitability

The CVSS score of 7.5 reflects a moderate‑to‑high severity. The EPSS score of < 1% indicates a very low probability of exploitation at this time, and the vulnerability is not listed in CISA’s KEV catalog. The likely attack vector is remote over the network: an attacker must be able to establish QUIC connections to the vulnerable service. If the application exposes HTTP/3 endpoints to the Internet or untrusted networks, the risk increases, as an attacker can repeatedly send crafted frames to trigger memory exhaustion.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to Netty version 4.2.16.Final or later to eliminate the buffer‑size verification flaw
  • If an upgrade is not immediately feasible, limit HTTP/3 traffic to trusted networks or disable HTTP/3 support until a patch is applied
  • Configure application‑level safeguards such as quota limits on QUIC stream payload sizes and monitor memory usage for anomalies

Generated by OpenCVE AI on August 4, 2026 at 00:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-hpcc-26xq-25fv Netty: Memory Exhaustion via HTTP/3 Reserved Frame Types
History
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
First Time appeared Netty
Netty netty
Vendors & Products Netty
Netty netty
Type Values Removed Values Added
Description Netty is a network application framework for development of protocol servers and clients. Prior to 4.2.16.Final, Netty's `Http3FrameCodec` buffers incoming data for HTTP/3 reserved frame types up to the wire-specified payload length without limits; `decodeFrame` trusts `payLoadLength`, allowing an attacker to open multiple QUIC streams and send reserved frames with very large payload lengths to cause memory exhaustion and denial of service. This issue is fixed in version 4.2.16.Final.
Title Netty: Memory Exhaustion via HTTP/3 Reserved Frame Types
Weaknesses CWE-400
References
Metrics cvssV3_1

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

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 22, 2026, 6:24 PM
Reserved
Jun 23, 2026, 2:55 PM
Status
Analyzed
Published
Jul 21, 2026, 10:17 PM
Modified
Aug 7, 2026, 8:47 PM