CVE-2026-61827: 
Java vulnerability analysis and mitigation

Overview

CVE-2026-61827 is an uncontrolled resource consumption vulnerability in the netty-incubator-codec-ohttp library's BinaryHttpParser, specifically in the Maven artifact io.netty.incubator:netty-incubator-codec-bhttp. The flaw arises because the parser does not enforce any limits on encoded variable lengths for fields, allowing a remote peer to cause the server to buffer data indefinitely, ultimately leading to an Out-of-Memory (OOM) condition. All versions up to and including 0.0.22.Final are affected; the issue was first disclosed on July 18, 2026, and published to the GitHub Advisory Database on August 20, 2026. It carries a CVSS v4 base score of 8.7 (High) (GitHub Advisory).

Technical details

The root cause is classified under CWE-400 (Uncontrolled Resource Consumption) and CWE-770 (Allocation of Resources Without Limits or Throttling). The BinaryHttpParser in the netty-incubator-codec-bhttp library processes encoded variable-length fields supplied by the remote peer without imposing any upper bound on their size. Because the remote peer fully controls these length values, a malicious peer can craft messages with arbitrarily large encoded field lengths, causing the server to continuously allocate memory buffers until the JVM runs out of heap space. No authentication or special privileges are required, and exploitation requires no user interaction (GitHub Advisory, Netty Security Advisory).

Impact

Successful exploitation results in a Denial of Service (DoS) through memory exhaustion (OOM crash) of the affected Java process. There is no impact on confidentiality or integrity — the vulnerability is purely an availability issue affecting the vulnerable system. Any service or application that uses netty-incubator-codec-bhttp version 0.0.22.Final or earlier to parse Binary HTTP messages is at risk of being rendered completely unavailable by a remote, unauthenticated attacker (GitHub Advisory).

Exploitability

No public proof-of-concept exploit code or in-the-wild exploitation has been reported as of the available data. The CVE status is listed as "Reserved," and no EPSS score or CISA KEV catalog entry is currently associated with this vulnerability. However, the attack requires no authentication, no user interaction, and low complexity, making it straightforward for any network-accessible attacker to attempt (GitHub Advisory, OSV).

Exploitation steps

  1. Reconnaissance: Identify services or applications that use the Maven artifact io.netty.incubator:netty-incubator-codec-bhttp at version 0.0.22.Final or earlier, particularly those exposing Binary HTTP (BHTTP) parsing endpoints over the network.
  2. Establish connection: Connect to the target service over the network — no credentials or prior access are required.
  3. Craft malicious BHTTP message: Construct a Binary HTTP message containing encoded variable-length field values with extremely large declared lengths (e.g., setting field length indicators to the maximum possible integer values).
  4. Send payload: Transmit the crafted message to the target's BHTTP parsing endpoint. The BinaryHttpParser will attempt to buffer the declared amount of data without enforcing any limit.
  5. Trigger OOM: Repeat or sustain the connection/message stream as needed; the server will continuously allocate heap memory until the JVM throws an OutOfMemoryError, crashing or severely degrading the service (GitHub Advisory).

Indicators of compromise

  • Logs: JVM crash logs or application logs showing java.lang.OutOfMemoryError: Java heap space errors originating from Netty's BHTTP parsing code paths.
  • Process: Sudden spike in JVM heap usage visible via JVM monitoring tools (e.g., JConsole, VisualVM, Prometheus JVM metrics) followed by process crash or GC thrashing.
  • Network: Unusual or sustained inbound connections to BHTTP-enabled endpoints sending large or malformed Binary HTTP messages; connections that remain open for extended periods without completing a valid request.
  • Application: Repeated service restarts or health check failures on applications using netty-incubator-codec-bhttp without other apparent cause (GitHub Advisory).

Mitigation and workarounds

Upgrade the Maven artifact io.netty.incubator:netty-incubator-codec-bhttp to version 0.0.23.Final, which enforces limits on encoded variable-length fields in the BinaryHttpParser. No official configuration-based workaround has been published; upgrading to the patched release is the recommended and primary remediation. Organizations should audit their dependency trees for transitive inclusion of affected versions and prioritize updating any internet-facing services (GitHub Advisory, Netty Release).

Community reactions

The advisory was published by Netty maintainer normanmaurer on July 18, 2026, and subsequently added to the GitHub Advisory Database on August 20, 2026. No significant broader media coverage, researcher commentary, or notable social media discussion has been identified for this vulnerability beyond the official advisory (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