PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-100656 – Denial of Service (Unbounded Memory Growth) – Netty HttpServerCodec (io.netty:nett

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-100656 is a denial-of-service vulnerability in Netty’s HttpServerCodec (io.netty:netty-codec-http), caused by unbounded per-connection queue growth when handling pipelined HTTP/1.1 requests. A remote, unauthenticated attacker can exploit this to force uncontrolled heap memory growth on the target server, exhausting available memory and disrupting service availability. The flaw carries a CVSS score of 8.7 (High).

Technical details

  • Root cause: HttpServerCodec tracks the HTTP method of each still-unanswered pipelined request on a connection. The first 32 pending entries are bit-packed into a single long, but any additional entries spill into methodOverflowQueue, a plain ArrayDeque<Byte> with no upper bound or capacity restriction.
  • Trigger conditions: An attacker opens a TCP connection to a Netty-based HTTP/1.1 server, pipelines a large number of requests on that single connection, and withholds reads on their own end so that responses are never flushed back. This allows the decoder to keep racing ahead of the application, continuously appending entries to the overflow queue.
  • Attack vector: Network-based, requires no authentication and no user interaction — a single TCP connection is sufficient.
  • Impact: Uncontrolled heap memory growth, leading to memory exhaustion and denial of service for the affected application/server. This mirrors an earlier, already-patched defect in the related HttpContentEncoder class (which received a maxPipelineDepth limit); HttpServerCodec, being a more foundational and widely used class in HTTP/1.1 servers, had not received the equivalent protection until this fix.

Affected software

  • io.netty:netty-codec-http versions 4.2.0.Final through 4.2.17.Final
  • io.netty:netty-codec-http versions up to and including 4.1.137.Final (4.1.x branch)

Severity

  • CVSS Score: 8.7 (High)
  • Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

Mitigation and recommended actions

  • Immediate: Upgrade to the patched releases:
    • 4.2.18.Final for the 4.2.x branch
    • 4.1.138.Final for the 4.1.x branch
  • If immediate patching is not possible:
    • Enforce connection-level limits such as maximum pipelined requests per connection, aggressive read/idle timeouts, and per-connection memory/resource caps at the load balancer or reverse proxy tier to reduce exposure to slow-read/pipelining abuse.
    • Monitor for connections exhibiting large numbers of pipelined requests combined with stalled or withheld reads, and terminate anomalous connections proactively.
    • Apply general resource-exhaustion protections (connection limits, memory watchdogs, autoscaling/restart policies) as a compensating control until the upgrade is applied.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge