NetSight
medium5.3

CVE-2026-69133

netty-incubator-codec-ohttp: OHTTP codecs retain consumed outer cumulation buffers after completed exchanges

Impact

netty-incubator-codec-ohttp implements Oblivious HTTP (OHTTP) gateway and client functionality using Netty. From 0.0.20.Final until 0.0.27.Final, OHttpClientCodec in codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpClientCodec.java and OHttpServerCodec in codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpServerCodec.java retain the consumed outer cumulationBuffer after a valid OHTTP exchange completes, even though OHttpRequestResponseContext.destroy in codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpRequestResponseContext.java releases the inner Binary HTTP cumulation and the channel remains active. A peer can complete a large request or response and leave the keep-alive connection idle, causing the client and server handlers to retain the current high-water pooled or direct buffer capacity until later inbound content replaces it or the handler is removed. Many long-lived idle connections can pin substantial memory and create availability pressure. The issue does not cause unbounded growth for repeated exchanges on a single channel. This issue is fixed in version 0.0.27.Final.

An attacker can exploit this over the network, without logging in, without any action by a user. If it succeeds: low risk of outages.

Affected packages

EcosystemPackageAffectedFixed in
mavenio.netty.incubator:netty-incubator-codec-ohttp>= 0.0.20.Final, <= 0.0.26.Final0.0.27.Final

Affected products · Netty

ProductAffected versions
Netty-incubator-codec-ohttp
from 0.0.20.Final, before 0.0.27.Final

Weakness classification

References