netty-incubator-codec-ohttp denial of service in BinaryHttpParser unbounded fields
Affects netty-incubator-codec-ohttp 0.0.22.Final and earlier. Fixed in 0.0.23.Final.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.0.23.Final
- Who is exposed
- Not reported
Summary
The netty-incubator-codec-ohttp library, which implements Oblivious HTTP gateway and client functionality on Netty, does not limit how much data a remote peer can make its BinaryHttpParser hold in variable-length fields. An attacker can reach this remotely, without logging in, by sending crafted messages that cause the decoder to keep buffering data until memory runs out, resulting in denial of service.
Written by a model
Original description
netty-incubator-codec-ohttp implements Oblivious HTTP (OHTTP) gateway and client functionality using Netty. Prior to 0.0.23.Final, BinaryHttpParser does not enforce limits on encoded variable-length fields controlled by a remote peer. A remote peer can cause the decoder to buffer data indefinitely until memory is exhausted, causing denial of service. This issue is fixed in version 0.0.23.Final.
Who should check
Teams running netty-incubator-codec-bhttp (netty-incubator-codec-ohttp) 0.0.22.Final or earlier that parse binary HTTP or Oblivious HTTP input from remote peers.
“io.netty.incubator:netty-incubator-codec-bhttp”
What to do
Upgrade to a fixed version: 0.0.23.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-61827 (netty-incubator-codec-ohttp: BinaryHttpParser should enforce limits for variable lengths fields), 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-61827 (entry last updated 2026-11-19):
Affected:
- netty netty-incubator-codec-ohttp: fixed in 0.0.23.Final
Fixed versions: 0.0.23.Final.
Conditions (all must be true for the bug to be hit):
- Affected versions are 0.0.22.Final and earlier. (source: https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-hmq9-67w8-j5pw)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-61827 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-61827 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-hmq9-67w8-j5pw
- https://github.com/netty/netty-incubator-codec-ohttp/commit/c5169de8814dbe730280fd793a0428a844e9045c
- https://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.23.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-61827
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-61827"}.Affected versions
- netty netty-incubator-codec-ohttpfixed in 0.0.23.Final
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 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-hmq9-67w8-j5pw |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-61827 |
| Record | NVD · CVE-2026-61827 |
| Other links 2 | |
| Repository | GitHub · netty/netty-incubator-codec-ohttp · Commit c5169de8 |
| Repository | GitHub · netty/netty-incubator-codec-ohttp · Release netty-incubator-codec-parent-ohttp-0.0.23.Final |
Questions about CVE-2026-61827
Is CVE-2026-61827 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
What does this mean?
BinaryHttpParser in netty-incubator-codec-ohttp does not enforce limits on variable-length fields when parsing binary HTTP messages. The advisory title describes this as the missing limit check.
Source: github.com, github.com
Which versions are affected by CVE-2026-61827?
netty-incubator-codec-ohttp: before 0.0.23.Final.
Source: cve.now feed data
Am I affected, and how do I check?
Versions 0.0.22.Final and earlier of netty-incubator-codec-ohttp are affected. To check a project, look at the netty-incubator-codec-ohttp version declared in its build or dependency files.
Source: github.com, github.com
How do I fix CVE-2026-61827?
Upgrade netty-incubator-codec-ohttp to 0.0.23.Final, which is the listed fixed version.
Source: github.com, github.com
Related
- 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
- CVE-2026-41207netty-incubator-codec-ohttp's HPKEContext operations may produce empty byte[] on failures
No corrections so far. Something wrong on this page? Report an error.