CVE-2026-100656: Netty HttpServerCodec Unbounded Queue Growth via HTTP/1.1 Pipelining

Published Sep 26, 2026
·
Updated

Netty (io.netty:netty-codec-http) contains an unbounded per-connection queue growth flaw in HttpServerCodec. The codec tracks the HTTP method of each still-unanswered pipelined request; the first 32 entries are bit-packed into a single long, but every additional entry is appended to methodOverflowQueue, an ArrayDeque with no size limit and no rejection path. A remote, unauthenticated attacker who pipelines HTTP/1.1 requests on a single connection while withholding reads on their own end (preventing responses from being flushed) can grow this queue without bound, causing unbounded heap growth and denial of service. Affected versions are 4.2.0.Final through 4.2.17.Final and all releases up to and including 4.1.137.Final; the issue is fixed in 4.2.18.Final and 4.1.138.Final.

Affected Software

1 affected component
maven/io.netty/netty-codec-http<=4.1.137.Final, >=4.2.0.Final<=4.2.17.Final

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade io.netty:netty-codec-http to a version that resolves this vulnerability.

    Fixed in 4.2.18.Final
  2. Upgrade

    Upgrade io.netty:netty-codec-http to a version that resolves this vulnerability.

    Fixed in 4.1.138.Final

Event History

Sep 26, 2026
CVE Published
via MITRE·01:23 PM
Data Sourced
via MITRE·01:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments using io.netty:netty-codec-http versions 4.2.0.Final through 4.2.17.Final, or any release up to and including 4.1.137.Final, are affected when HttpServerCodec processes HTTP/1.1 connections.

2

What must an attacker do to trigger the denial of service?

An unauthenticated remote attacker must send pipelined HTTP/1.1 requests over a single connection and withhold reading responses. This prevents responses from being flushed and allows the per-connection method queue to grow without bound.

3

Is authentication or user interaction required for exploitation?

No. The issue is network-reachable with low attack complexity and requires neither privileges nor user interaction.

4

What is the remediation?

Upgrade to Netty 4.2.18.Final or 4.1.138.Final, which contain the fix.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203