
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-69133 is a memory retention vulnerability in netty-incubator-codec-ohttp, the Netty-based Oblivious HTTP (OHTTP) codec library. Both OHttpClientCodec and OHttpServerCodec fail to release the outer cumulationBuffer after a valid OHTTP exchange completes, retaining pooled or direct buffer capacity at its peak (high-water mark) for the lifetime of an idle keep-alive connection. Affected versions span from 0.0.20.Final through 0.0.26.Final (inclusive); the issue is fixed in 0.0.27.Final. It carries a CVSS v3.1 base score of 5.3 (Medium) (Github Advisory, Netty Advisory).
The root cause is classified as CWE-772 (Missing Release of Resource after Effective Lifetime). In both OHttpClientCodec and OHttpServerCodec, inbound encrypted HTTP content is accumulated into a handler-level cumulationBuffer. Upon processing LastHttpContent, the codec destroys the OHttpRequestResponseContext (releasing only the inner Binary HTTP cumulation), but does not release or reset the outer cumulationBuffer. That buffer is only freed in handlerRemoved() — i.e., when the handler is removed or the channel is closed — not immediately after exchange completion. An attacker can exploit this by completing a large valid OHTTP request or response and then leaving the keep-alive connection idle, causing the codec to pin the high-water buffer capacity (observed at up to 262,144 bytes per connection in PoC testing) for the connection's lifetime. The fix, applied in commit a82cd85, discards read bytes or releases the buffer entirely in the completed-exchange path when no unread bytes remain (Netty Advisory, Fix Commit).
The vulnerability has no confidentiality or integrity impact; its sole effect is on availability. An unauthenticated remote attacker can open many long-lived idle keep-alive connections, each pinning a large pooled or direct buffer at its peak capacity, collectively exhausting JVM heap or native direct memory on the affected service. This creates availability pressure that can degrade or deny service to legitimate users. The impact is bounded per channel — it does not cause unbounded growth from repeated exchanges on a single connection — but scales linearly with the number of concurrent idle connections an attacker can maintain (Github Advisory).
A proof-of-concept test (OHttpCumulationBufferRetentionTest) is publicly documented in the security advisory, demonstrating buffer retention via reflection on EmbeddedChannel pairs using BouncyCastle HPKE helpers. The exploit requires no authentication and no user interaction, and is automatable over the network. The EPSS score is approximately 0.304%, indicating low but non-negligible probability of exploitation in the wild. There is no evidence of active in-the-wild exploitation, no threat actor attribution, and the vulnerability is not listed in the CISA KEV catalog (Netty Advisory, Github Advisory).
netty-incubator-codec-ohttp versions 0.0.20.Final through 0.0.26.Final that exposes an OHTTP gateway endpoint over the network.cumulationBuffer (~262,144 bytes capacity).cumulationBuffer at peak capacity with refCnt=1 and readableBytes=0.java.lang.OutOfMemoryError: Direct buffer memory errors in application logs.io.netty.allocator.usedDirectMemory or pooled buffer metrics correlated with idle connection count rather than active request rate (Netty Advisory).Upgrade io.netty.incubator:netty-incubator-codec-ohttp to version 0.0.27.Final or later, which releases or discards the outer cumulationBuffer immediately after a completed exchange (Release Tag, Fix Commit). As a workaround for deployments that cannot upgrade immediately, configure aggressive connection idle timeouts to close long-lived idle keep-alive connections and force buffer release. Additionally, monitor JVM direct memory and heap usage on OHTTP-serving nodes and set alerts for anomalous growth correlated with idle connection counts (Github Advisory).
The vulnerability was reported by researcher VuiVeIshere and the advisory was published by Netty maintainer normanmaurer. No significant broader media coverage or notable social media commentary has been identified beyond the GitHub security advisory itself.
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."