netty-incubator-codec-ohttp: Binary HTTP parser infinite loop on known-length field section boundary

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary io.netty.incubator:netty-incubator-codec-bhttp can enter a non-terminating parse loop when a known-length Binary HTTP field section ends exactly after a complete field line. A remote peer that can send Binary HTTP input to a Netty pipeline using BinaryHttpParser / BinaryHttpDecoder can use a tiny malformed request or response to keep the parsing thread busy indefinitely, causing denial of service. Details In codec-bhttp/src/main/java/io/netty/incubator/codec/bhttp/BinaryHttpParser.java, readFieldSection(...) tracks the remaining field-section length in fieldSectionLength, then repeatedly calls readFieldLine(...) until the length reaches zero: - readFieldSection(...) parses the known-length field section and enters while (fieldSectionLength != 0) at BinaryHttpParser.java:619. - Inside the loop, it records readableBytes, calls readFieldLine(...), computes read = readableBytes - in.readableBytes(), asserts read 0, and subtracts read from fieldSectionLength at…

Published by the source

20 Aug 2026, 18:43 UTC

Last modified by the source

20 Aug 2026, 19:11 UTC

Source last checked

26 Oct 2026, 16:54 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-8cfx-wx3q-mh5q

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8cfx-wx3q-mh5q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-63124

Advisory: netty-incubator-codec-ohttp: Binary HTTP parser infinite loop on known-length field section boundary
IDs: CVE-2026-63124, GHSA-8cfx-wx3q-mh5q
Record: https://patchnext.com/advisories/cve-2026-63124 (revision 2, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.netty.incubator:netty-incubator-codec-bhttp 0.0.23.Final. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.netty.incubator:netty-incubator-codec-bhttp: affected <= 0.0.22.Final; fixed in 0.0.23.Final

## Suggested inspection (read-only)
- Maven io.netty.incubator:netty-incubator-codec-bhttp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.netty.incubator:netty-incubator-codec-bhttp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8cfx-wx3q-mh5q (OSV record GHSA-8cfx-wx3q-mh5q lists affected ranges: Maven io.netty.incubator:netty-incubator-codec-bhttp >=0 <0.0.23.Final (fixed))
- Verified: https://github.com/advisories/GHSA-8cfx-wx3q-mh5q (GitHub-reviewed advisory GHSA-8cfx-wx3q-mh5q lists affected ranges: Maven io.netty.incubator:netty-incubator-codec-bhttp >=0 <=0.0.22.Final)

Commands are suggestions: review each one before running it.