Skip to main content
Menu
CVEs

netty-incubator-codec-ohttp denial of service in BinaryHttpParser field decoding

Affects netty-incubator-codec-ohttp 0.0.22.Final and earlier, reached through the auto-wired OHTTP server and client codecs. Fixed in 0.0.23.Final.

CVE-2026-63202Published November 19, 2026, updated

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.0.23.Final
Who is exposed
Default setups

Summary

The netty-incubator-codec-ohttp software has a flaw in its Binary HTTP parser that lets a remote attacker, without logging in, send specially crafted encrypted content that pins a processing thread at full CPU in an endless loop. Repeated requests can exhaust the event-loop threads and deny service until the software is restarted.

Written by a model

Original description

netty-incubator-codec-ohttp implements Oblivious HTTP (OHTTP) gateway and client functionality using Netty. Prior to 0.0.23.Final, BinaryHttpParser.readFieldSection in codec-bhttp/src/main/java/io/netty/incubator/codec/bhttp/BinaryHttpParser.java loops while fieldSectionLength is nonzero and relies on disabled-by-default assertions to require BinaryHttpParser.readFieldLine to return a value and consume bytes. A corrupt field line can consume more bytes than its understated declared section length and drive the counter negative, or a truncated field line can return without consuming data and leave the parser in the same state. An unauthenticated OHTTP peer can encrypt such Binary HTTP content under the gateway public configuration, reach OHttpRequestResponseContext.ContentDecoder.decodeChunk, and permanently pin a Netty event-loop thread at full CPU before application business logic. Multiple requests can exhaust the event-loop group and deny service until restart. This issue is fixed in version 0.0.23.Final.

Who should check

Teams running netty-incubator-codec-ohttp 0.0.22.Final or earlier, including OHTTP gateways and clients built on the auto-wired BHTTP/OHTTP codecs.

“Affected version: netty-incubator-codec-ohttp HEAD d3f2b49 (release 0.0.22.Final + 3 commits)”

github.com

What to do

  1. Check every install: default setups are affected.

  2. Upgrade to a fixed version: 0.0.23.Final.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-63202 (netty-incubator-codec-ohttp BinaryHttpParser: Unauthenticated CPU-exhaustion DoS via infinite loop in field-section decoding), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-63202 (entry last updated 2026-11-19):
Affected:
- netty netty-incubator-codec-ohttp: fixed in 0.0.23.Final
Fixed versions: 0.0.23.Final.
Conditions (all must be true for the bug to be hit):
- Affected: netty-incubator-codec-ohttp release 0.0.22.Final and earlier (up to the 0.0.23.Final fix). (source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-4899-mpch-38p3)
- Reached through the auto-wired OHTTP server and client codecs. (source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-4899-mpch-38p3)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-63202 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63202 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-4899-mpch-38p3
- https://github.com/netty/netty-incubator-codec-ohttp/commit/89d6cfc67e034a92e6eef9ccb9829b6e358a91ea
- https://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.23.Final
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-63202
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-63202"}.

Affected versions

cve.now Index

30Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure22/25Default setups, reachable over the network without a login
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 70 if added to CISA KEV
  • Would score about 65 if CISA's SSVC rates exploitation active

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 5

Questions about CVE-2026-63202

Is CVE-2026-63202 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

A malicious request can make the BinaryHttpParser get stuck in an infinite loop while decoding a field section. Each such request keeps one Netty event-loop thread at 100% CPU, and enough of them can exhaust the event-loop group until the service is restarted. No authentication is needed.

Source: github.com, github.com

Which versions are affected by CVE-2026-63202?

netty-incubator-codec-ohttp: before 0.0.23.Final.

Source: cve.now feed data

Am I affected, and how do I check?

Versions of netty-incubator-codec-ohttp up to 0.0.22.Final are affected, including development builds based on that release. The issue is reached through the auto-wired OHTTP server and client codecs. To check, look at the netty-incubator-codec-ohttp version in your build file or dependency list.

Source: github.com, github.com

How do I fix CVE-2026-63202?

Upgrade netty-incubator-codec-ohttp to 0.0.23.Final, which contains the fix.

Source: github.com, github.com

No corrections so far. Something wrong on this page? Report an error.