{"vuln_id":"CVE-2026-69133","aliases":["GHSA-cg26-4c6j-2x8h"],"description":"netty-incubator-codec-ohttp: OHTTP codecs retain consumed outer cumulation buffers after completed exchanges","published_at":"2026-11-19T22:18:08.440000Z","modified_at":"2026-11-20T17:18:26.447000Z","first_seen_at":"2026-11-21T19:15:19.254742Z","severity":"medium","severity_source":"nvd","cvss_score":5.3,"cvss_vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","cwe":["CWE-772"],"vendor":null,"product":null,"kev":{"is_kev":false,"date_added":null,"due_date":null,"ransomware":false},"epss":0.00476,"epss_percentile":0.41973,"nvd_status":"Deferred","enriched_at":null,"links":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-69133"},"matched_alias":null,"items":[{"id":10995,"source":{"id":"osv","name":"OSV.dev"},"title":"GHSA-cg26-4c6j-2x8h: netty-incubator-codec-ohttp: OHTTP codecs retain consumed outer cumulation buffers after completed exchanges","summary":"netty-incubator-codec-ohttp: OHTTP codecs retain consumed outer cumulation buffers after completed exchanges\n\n## Summary:\n\nOHttpClientCodec 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.\n\nThis can pin attacker-influenced pooled/direct buffer capacity on idle keep-alive channels. Across many long-lived idle connections, this can create availability pressure.\n\nAffected components:\n\n* codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpClientCodec.java\n* codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpServerCodec.java\n* codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpRequestResponseContext.java\n\n## Root cause:\n\nOHttpClientCodec 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.\n\nOHttpServerCodec 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.\n\nOHttpRequestResponseContext.parse() consumes bytes from the caller-provided outer cumulation buffer, but its destroy() path releases only the inner binary HTTP cumulation, not the codec-level outer cumulationBuffer.\n\n## PoC:\n\nA local test only:\n\n```\ncodec-ohttp/src/test/java/io/netty/incubator/codec/ohttp/OHttpCumulationBufferRetentionTest.java\n```\n\nThe test reuses existing OHTTP test helpers and BouncyCastle crypto provider to perform valid completed OHTTP exchanges over EmbeddedChannel pairs. It sends both a small and a large request/response exchange, confirms completion, then reflects the private cumulationBuffer field from both OHttpClientCodec and OHttpServerCodec.\n\nCommand:\n\n```\n./mvnw -pl codec-ohttp -Dtest=OHttpCumulationBufferRetentionTest -DfailIfNoTests=false test\n```\n\nObserved output:\n\n```\nsmall client after completion: refCnt=1 capacity=1064 readerIndex=1064 writerIndex=1064 readableBytes=0\nsmall server after completion: refCnt=1 capacity=1110 readerIndex=1110 writerIndex=1110 readableBytes=0\nlarge client after completion: refCnt=1 capacity=262144 readerIndex=131114 writerIndex=131114 readableBytes=0\nlarge server after completion: refCnt=1 capacity=262144 readerIndex=131160 writerIndex=131160 readableBytes=0\nsmall after close: clientOldRefCnt=0 serverOldRefCnt=0\nlarge after close: clientOldRefCnt=0 serverOldRefCnt=0\nTests run: 1, Failures: 0, Errors: 0, Skipped: 0\nBUILD SUCCESS\n```\n\nInterpretation:\n\nAfter completion, both the client and server cumulationBuffer objects have:\n\n* refCnt=1\n* readableBytes=0\n* large retained capacity for t\n\nAffected: Maven:io.netty.incubator:netty-incubator-codec-ohttp\n\nFixed in: 0.0.27.Final\n\nReferences:\nhttps://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-cg26-4c6j-2x8h\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-69133\nhttps://github.com/netty/netty-incubator-codec-ohttp/commit/a82cd85099c1a1fb78b73b068c77c8c902fc32ce\nhttps://github.com/netty/netty-incubator-codec-ohttp\nhttps://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.27.Final","url":"https://osv.dev/vulnerability/GHSA-cg26-4c6j-2x8h","published_at":"2026-11-20T16:22:09Z","updated_at":"2026-11-20T16:30:04.228142Z","fetched_at":"2026-11-21T19:15:55.946357Z","severity":"medium","cvss_score":5.3,"epss":0.00476,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":"io.netty.incubator:netty-incubator-codec-ohttp","vuln_id":"CVE-2026-69133","vuln_ids":["CVE-2026-69133","GHSA-CG26-4C6J-2X8H"],"tags":["osv","maven","fix-available"],"cluster_id":2014,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/10995","html":"https://vulnwatch.ve1ve2.com/item/10995"}},{"id":2298,"source":{"id":"ghsa","name":"GitHub Security Advisories"},"title":"GHSA-cg26-4c6j-2x8h / CVE-2026-69133: netty-incubator-codec-ohttp: OHTTP codecs retain consumed outer cumulation buffers after completed exchanges","summary":"netty-incubator-codec-ohttp: OHTTP codecs retain consumed outer cumulation buffers after completed exchanges\n\n## Summary:\n\nOHttpClientCodec 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.\n\nThis can pin attacker-influenced pooled/direct buffer capacity on idle keep-alive channels. Across many long-lived idle connections, this can create availability pressure.\n\nAffected components:\n\n* codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpClientCodec.java\n* codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpServerCodec.java\n* codec-ohttp/src/main/java/io/netty/incubator/codec/ohttp/OHttpRequestResponseContext.java\n\n## Root cause:\n\nOHttpClientCodec 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.\n\nOHttpServerCodec 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.\n\nOHttpRequestResponseContext.parse() consumes bytes from the caller-provided outer cumulation buffer, but its destroy() path releases only the inner binary HTTP cumulation, not the codec-level outer cumulationBuffer.\n\n## PoC:\n\nA local test only:\n\n```\ncodec-ohttp/src/test/java/io/netty/incubator/codec/ohttp/OHttpCumulationBufferRetentionTest.java\n```\n\nThe test reuses existing OHTTP test helpers and BouncyCastle crypto provider to perform valid completed OHTTP exchanges over EmbeddedChannel pairs. It sends both a small and a large request/response exchange, confirms completion, then reflects the private cumulationBuffer field from both OHttpClientCodec and OHttpServerCodec.\n\nCommand:\n\n```\n./mvnw -pl codec-ohttp -Dtest=OHttpCumulationBufferRetentionTest -DfailIfNoTests=false test\n```\n\nObserved output:\n\n```\nsmall client after completion: refCnt=1 capacity=1064 readerIndex=1064 writerIndex=1064 readableBytes=0\nsmall server after completion: refCnt=1 capacity=1110 readerIndex=1110 writerIndex=1110 readableBytes=0\nlarge client after completion: refCnt=1 capacity=262144 readerIndex=131114 writerIndex=131114 readableBytes=0\nlarge server after completion: refCnt=1 capacity=262144 readerIndex=131160 writerIndex=131160 readableBytes=0\nsmall after close: clientOldRefCnt=0 serverOldRefCnt=0\nlarge after close: clientOldRefCnt=0 serverOldRefCnt=0\nTests run: 1, Failures: 0, Errors: 0, Skipped: 0\nBUILD SUCCESS\n```\n\nInterpretation:\n\nAfter completion, both the client and server cumulationBuffer objects have:\n\n* refCnt=1\n* readableBytes=0\n* large retained capacity for t\n\nAffected packages: maven:io.netty.incubator:netty-incubator-codec-ohttp\nPatched: io.netty.incubator:netty-incubator-codec-ohttp 0.0.27.Final","url":"https://github.com/advisories/GHSA-cg26-4c6j-2x8h","published_at":"2026-11-20T16:22:09Z","updated_at":"2026-11-20T16:22:10Z","fetched_at":"2026-11-21T19:15:18.416731Z","severity":"medium","cvss_score":5.3,"epss":0.00476,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":"io.netty.incubator:netty-incubator-codec-ohttp","vuln_id":"CVE-2026-69133","vuln_ids":["CVE-2026-69133","GHSA-CG26-4C6J-2X8H"],"tags":["ghsa","maven","CWE-772"],"cluster_id":2014,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/2298","html":"https://vulnwatch.ve1ve2.com/item/2298"}},{"id":9324,"source":{"id":"nvd","name":"NVD CVE API 2.0"},"title":"CVE-2026-69133: netty-incubator-codec-ohttp implements Oblivious HTTP (OHTTP) gateway and client functionality using Netty. From 0.0.20.Final until 0.0.27.Final, OHttpClientCo…","summary":"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.\n\nReferences:\nhttps://github.com/netty/netty-incubator-codec-ohttp/commit/a82cd85099c1a1fb78b73b068c77c8c902fc32ce\nhttps://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.27.Final\nhttps://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-cg26-4c6j-2x8h\nhttps://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-cg26-4c6j-2x8h","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-69133","published_at":"2026-11-19T22:18:08.440000Z","updated_at":"2026-11-20T17:18:26.447000Z","fetched_at":"2026-11-21T19:15:31.484929Z","severity":"medium","cvss_score":5.3,"epss":0.00476,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":null,"vuln_id":"CVE-2026-69133","vuln_ids":["CVE-2026-69133","GHSA-CG26-4C6J-2X8H"],"tags":["CWE-772"],"cluster_id":2015,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/9324","html":"https://vulnwatch.ve1ve2.com/item/9324"}}]}