Answer in brief
CVE-2026-61799 records a Medium severity (CVSS 5.3) vulnerability in netty-incubator-codec-ohttp: Binary HTTP parser unchecked varint length overflow causes decoder crash. 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 5.3. 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 in codec-bhttp/src/main/java/io/netty/incubator/codec/bhttp/BinaryHttpParser.java accumulates attacker-controlled Binary HTTP variable-length integers into the int offset sumBytes. BinaryHttpParser.readRequestHead, BinaryHttpParser.readFieldLine, and BinaryHttpParser.getIndeterminateLength can narrow long lengths into that offset, causing integer wraparound before buffer indices are calculated. A remote peer that supplies a valid large encoded length to BinaryHttpParser or BinaryHttpDecoder can trigger an unchecked bounds exception from a small malformed message, fail or close the channel, and repeatedly cause denial of service. Java and Netty bounds checks prevent memory corruption, and no information disclosure was observed. This issue is fixed in version 0.0.23.Final.
Quoted source text, attributed separately from HOL analysis.