CVE-2026-63124: 
Java vulnerability analysis and mitigation

Overview

CVE-2026-63124 is a denial-of-service vulnerability in the io.netty.incubator:netty-incubator-codec-bhttp Maven package (part of the netty-incubator-codec-ohttp project) caused by an infinite loop in the Binary HTTP parser. When a known-length Binary HTTP field section ends exactly after a complete field line, the BinaryHttpParser / BinaryHttpDecoder enters a non-terminating parse loop, allowing a remote unauthenticated attacker to hang the parsing thread indefinitely. All versions up to and including 0.0.22.Final are affected; the issue was fixed in 0.0.23.Final. The vulnerability was originally published on July 12, 2026, and added to the GitHub Advisory Database on August 20, 2026, with a CVSS v3.1 base score of 7.5 (High) (Github Advisory, Netty Advisory).

Technical details

The root cause is classified as CWE-400 (Uncontrolled Resource Consumption) and CWE-835 (Loop with Unreachable Exit Condition). In BinaryHttpParser.java, the readFieldSection(...) method tracks remaining field-section length in fieldSectionLength and loops with while (fieldSectionLength != 0) (line 619). Inside the loop, it calls readFieldLine(...), computes bytes consumed as read = readableBytes - in.readableBytes(), and subtracts read from fieldSectionLength. However, readFieldLine(...) returns null without consuming any bytes when a field line ends exactly at the boundary of the readable slice (lines 678–681), due to the check if (sumBytes >= in.readableBytes()) return null. Because the assert read > 0 guard is inactive under production JVM settings (assertions disabled by default), the loop subtracts zero indefinitely and never exits. The boundary condition is triggered by a minimal valid known-length field section — for example, a field section of length 4 with a single field line (name a, value b) — requiring no authentication or special privileges (Github Advisory, Netty Advisory).

Impact

Successful exploitation pins the Netty event-loop thread or worker responsible for the affected channel, preventing it from processing any other channels on the same event loop and causing a denial of service. Because Netty's event-loop model is shared across many connections, a single malicious connection can degrade or eliminate availability for all other clients served by the same loop. Additionally, through OHTTP, the same BinaryHttpParser is invoked after decryption of protected payloads, meaning authenticated or decryptable OHTTP peers can also trigger the infinite loop in the inner BHTTP parser. There is no confidentiality or integrity impact (Github Advisory, Netty Advisory).

Exploitability

A public proof-of-concept is included in the GitHub Security Advisory, demonstrating that a minimal Java program can reproduce the hang within seconds using a crafted BHTTP buffer with no special tooling required. No authentication or elevated privileges are needed; any remote peer capable of sending Binary HTTP input to a vulnerable Netty pipeline can trigger the condition. There is no evidence of in-the-wild exploitation or threat actor attribution at this time, and the CVE status remains "Reserved." No EPSS score or CISA KEV listing has been reported (Github Advisory, Netty Advisory).

Exploitation steps

  1. Identify target: Locate a service running a Netty pipeline that uses BinaryHttpParser or BinaryHttpDecoder from io.netty.incubator:netty-incubator-codec-bhttp version <= 0.0.22.Final, either directly or via OHTTP.
  2. Craft malicious BHTTP payload: Construct a known-length Binary HTTP request where the field section length exactly matches the byte length of a single complete field line with no trailing byte. Example: field section length = 4, name length = 1, name = a, value length = 1, value = b.
  3. Send the payload: Deliver the crafted BHTTP bytes to the target Netty channel (e.g., via a raw TCP/TLS connection or an OHTTP-encapsulated request if the target uses OHTTP).
  4. Trigger infinite loop: The readFieldSection(...) method enters while (fieldSectionLength != 0), calls readFieldLine(...) which returns null without consuming bytes, subtracts zero from fieldSectionLength, and loops forever — pinning the event-loop thread.
  5. Achieve denial of service: The pinned thread can no longer process other channels on the same event loop, degrading or eliminating service availability for all other clients (Github Advisory, Netty Advisory).

Indicators of compromise

  • Process: Netty event-loop or worker threads showing 100% CPU utilization sustained over time with no corresponding increase in throughput; JVM thread dumps revealing a thread stuck in BinaryHttpParser.readFieldSection() or BinaryHttpParser.readFieldLine().
  • Network: Incoming connections sending small, well-formed Binary HTTP requests (a few bytes) that do not complete or receive a response; connections from unexpected peers to BHTTP/OHTTP endpoints.
  • Logs: Application logs showing channels becoming unresponsive or timing out; absence of normal request processing logs after a specific connection is established; JVM thread dump logs indicating a thread blocked indefinitely in io.netty.incubator.codec.bhttp.BinaryHttpParser.

Mitigation and workarounds

Upgrade io.netty.incubator:netty-incubator-codec-bhttp to version 0.0.23.Final, which is the patched release that resolves the infinite loop (Netty Release). As a temporary workaround prior to upgrading, enabling JVM assertions (-ea flag) will cause the assert read > 0 check to throw an AssertionError on the malformed input, preventing the infinite loop — however, this is not recommended for production as it may affect performance and other assertion behavior. Network-level controls such as restricting access to BHTTP/OHTTP endpoints to trusted peers can reduce exposure until patching is complete (Github Advisory).

Community reactions

The vulnerability was discovered and reported by Thai Son Dinh (sondt99 / VuiVeIshere) from VinSOC Labs (R&D), and the advisory was published by Netty maintainer normanmaurer on July 12, 2026. No significant broader media coverage or notable public social media discussion has been identified beyond the GitHub advisory and OSV database entry (Github Advisory).

Additional resources


Source: This report was generated using AI

Related Java vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-61827HIGH8.7
  • Java logoJava
  • io.netty.incubator:netty-incubator-codec-bhttp
NoYesNov 19, 2026
CVE-2026-63202HIGH7.5
  • Java logoJava
  • io.netty.incubator:netty-incubator-codec-bhttp
NoYesNov 19, 2026
CVE-2026-63124HIGH7.5
  • Java logoJava
  • io.netty.incubator:netty-incubator-codec-bhttp
NoYesNov 19, 2026
CVE-2026-69133MEDIUM5.3
  • Java logoJava
  • io.netty.incubator:netty-incubator-codec-ohttp
NoYesNov 19, 2026
CVE-2026-61799MEDIUM5.3
  • Java logoJava
  • io.netty.incubator:netty-incubator-codec-bhttp
NoYesNov 19, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management