Skip to main content
Menu
CVEs

netty-incubator-codec-ohttp denial of service in Binary HTTP parser

Affects netty-incubator-codec-ohttp before 0.0.23.Final when parsing known-length Binary HTTP field sections that end exactly after a complete field line. Fixed in 0.0.23.Final.

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

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 0.0.23.Final
Who is exposed
Not reported

Summary

The netty-incubator-codec-ohttp library, which implements Oblivious HTTP gateway and client functionality, can get stuck in an endless loop in its Binary HTTP parser. A remote peer without credentials can send a known-length header or trailer section that ends at a specific boundary, tying up the event-loop or worker thread handling that connection.

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.readFieldLine in codec-bhttp/src/main/java/io/netty/incubator/codec/bhttp/BinaryHttpParser.java treats a complete field line that ends exactly at a known field-section boundary as incomplete and returns without consuming bytes. BinaryHttpParser.readFieldSection then leaves fieldSectionLength unchanged and repeats the loop because its forward-progress checks are Java assertions, which are normally disabled in production. A remote peer that sends a known-length Binary HTTP header or trailer section ending at that boundary can make the parser spin indefinitely and pin the Netty event-loop or worker thread responsible for the channel. This issue is fixed in version 0.0.23.Final.

Who should check

Teams running netty-incubator-codec-bhttp or netty-incubator-codec-ohttp up to 0.0.22.Final, including OHTTP gateways and clients and any Netty pipeline using BinaryHttpDecoder.

“Affected versions <= 0.0.22.Final”

github.com

What to do

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-63124 (netty-incubator-codec-ohttp: Binary HTTP parser infinite loop on known-length field section boundary), 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-63124 (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):
- A known-length Binary HTTP header or trailer field section that ends exactly after a complete field line. (source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-8cfx-wx3q-mh5q)
- JVM assertions disabled, the production default, so the forward-progress assert does not stop the loop. (source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-8cfx-wx3q-mh5q)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-63124 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63124 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-8cfx-wx3q-mh5q
- https://github.com/netty/netty-incubator-codec-ohttp/commit/88a244eeb27827698f7843e9d80c0db335df5559
- 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-63124
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-63124"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • 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
  • Would score about 30 if advisories confirm default setups are exposed

Timeline

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

Evidence 5

Questions about CVE-2026-63124

Is CVE-2026-63124 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?

The Binary HTTP parser can loop forever when a known-length header or trailer field section ends exactly after a complete field line. This causes denial of service, and the loop can pin the event-loop or worker thread handling the channel.

Source: github.com

Which versions are affected by CVE-2026-63124?

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 before 0.0.23.Final are affected when they parse known-length Binary HTTP field sections. The loop occurs with JVM assertions disabled, which is the production default. To check a project, look at the netty-incubator-codec-ohttp version in its build file or dependency tree.

Source: github.com

How do I fix CVE-2026-63124?

Upgrade netty-incubator-codec-ohttp to 0.0.23.Final or later.

Source: github.com

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