CVE-2026-69133

GHSA-cg26-4c6j-2x8h · published 19 Nov 2026 · updated 20 Nov 2026

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

5.3MediumCVSS 5.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in io.netty.incubator:netty-incubator-codec-ohttp 0.0.27.Final.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
netty>=0.0.20.Final <0.0.27.Final
maven: io.netty.incubator:netty-incubator-codec-ohttp>=0.0.20.Final <=0.0.26.Final0.0.27.Final

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-69133 severity on Zeptric[![CVE-2026-69133](https://zeptric.io/badge/cve/CVE-2026-69133.svg)](https://zeptric.io/cve/CVE-2026-69133)