netty-incubator-codec-ohttp unauthenticated memory exhaustion in OHTTP codecs
- Exploited
- No known exploitation
- Fix
- Fixed in 0.0.27.Final
- Who is exposed
- Not reported
Summary
The netty-incubator-codec-ohttp library's OHTTP client and server codecs keep a large inbound buffer allocated after an exchange completes, even while the connection stays open and idle. A remote peer without logging in can trigger this by sending a large request or response and then leaving the keep-alive connection idle, so many such connections can tie up substantial memory and strain availability.
Written by a model
Original description
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.
What to do
Upgrade to a fixed version: 0.0.27.Final.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-69133 (netty-incubator-codec-ohttp: OHTTP codecs retain consumed outer cumulation buffers after completed exchanges), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-69133 (entry last updated 2026-11-19):
Affected:
- netty netty-incubator-codec-ohttp: from 0.0.20.Final, fixed in 0.0.27.Final
Fixed versions: 0.0.27.Final.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-69133 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-69133 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-cg26-4c6j-2x8h
- https://github.com/netty/netty-incubator-codec-ohttp/commit/a82cd85099c1a1fb78b73b068c77c8c902fc32ce
- https://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.27.Final
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-69133
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-69133"}.Affected versions
- netty netty-incubator-codec-ohttpFrom 0.0.20.Final · fixed in 0.0.27.Final
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · netty/netty-incubator-codec-ohttp · Advisory GHSA-cg26-4c6j-2x8h |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-69133 |
| Record | NVD · CVE-2026-69133 |
| Other links 2 | |
| Repository | GitHub · netty/netty-incubator-codec-ohttp · Commit a82cd850 |
| Repository | GitHub · netty/netty-incubator-codec-ohttp · Release netty-incubator-codec-parent-ohttp-0.0.27.Final |
Questions about CVE-2026-69133
Is CVE-2026-69133 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-69133?
netty-incubator-codec-ohttp: from 0.0.20.Final before 0.0.27.Final.
Source: cve.now feed data
How do I fix CVE-2026-69133?
Upgrade to a fixed version: 0.0.27.Final.
Source: cve.now feed data
Related
- CVE-2026-61827netty-incubator-codec-ohttp: BinaryHttpParser should enforce limits for variable lengths fields
- CVE-2026-54251netty-incubator-codec-ohttp: [OHttpServerCodec] Native Direct-Memory Leak on AEAD Decryption Failure Leads to Gateway Denial of Service
- CVE-2026-61798netty-incubator-codec-ohttp: BoringSSL HPKE private key bytes exposed through toString() and exception messages
- CVE-2024-40642Absent Input Validation in BinaryHttpParser in the netty incubator codec.bhttp
- CVE-2026-63202netty-incubator-codec-ohttp BinaryHttpParser: Unauthenticated CPU-exhaustion DoS via infinite loop in field-section decoding
- CVE-2026-63124netty-incubator-codec-ohttp: Binary HTTP parser infinite loop on known-length field section boundary
No corrections so far. Something wrong on this page? Report an error.