- Severity: MEDIUM
- CVE: CVE-2026-69133
- Ecosystems: maven
- Packages: io.netty.incubator:netty-incubator-codec-ohttp
## Summary:
OHttpClientCodec and OHttpServerCodec retain the encrypted outer HttpContent in a handler-level cumulationBuffer. After a valid OHTTP exchange completes, the OHTTP request/response context is destroyed, but the outer cumulationBuffer is not released or reset. It remains referenced by the codec until a later inbound content frame replaces it or the handler is removed/channel is closed.
This can pin attacker-influenced pooled/direct buffer capacity on idle keep-alive channels. Across many long-lived idle connections, this can create availability pressure.
Affected components:
* codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpClientCodec.java
* codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpServerCodec.java
* codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpRequestResponseContext.java
## Root cause:
OHttpClientCodec retains inbound content into a handler-level cumulationBuffer. On LastHttpContent, it destroys only the OHttpRequestResponseContextHolder. The cumulationBuffer is released in handlerRemoved(), not immediately after successful exchange completion.
OHttpServerCodec follows the same pattern: it retains inbound content into a handler-level cumulationBuffer, and on completed request/response it destroys the OHttpRequestResponseContext. The outer cumulationBuffer remains owned by the codec and is released only when the handler is removed.
OHttpRequestResponseContext.parse() consumes bytes from the caller-provide…
Source: GitHub Security Advisories · 2026-11-20