Answer in brief
CVE-2026-63124 records a High severity (CVSS 7.5) vulnerability in netty-incubator-codec-ohttp: Binary HTTP parser infinite loop on known-length field section boundary. The current sources do not mark it as known exploited. The current feed maps netty/netty-incubator-codec-ohttp (generic), io.netty.incubator:netty-incubator-codec-bhttp (maven), io.netty.incubator:netty-incubator-codec-bhttp (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps netty/netty-incubator-codec-ohttp (generic), io.netty.incubator:netty-incubator-codec-bhttp (maven), io.netty.incubator:netty-incubator-codec-bhttp (maven). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| netty/netty-incubator-codec-ohttpgeneric | <0.0.23.Final | 0.0.23.Final |
| io.netty.incubator:netty-incubator-codec-bhttpmaven | >=0 <0.0.23.Final | 0.0.23.Final |
| io.netty.incubator:netty-incubator-codec-bhttpmaven | <=0.0.22.Final | 0.0.23.Final |
Published upstream
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 20, 2026
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.
Quoted source text, attributed separately from HOL analysis.