Skip to main content
Menu
CVEs

netty-incubator-codec-ohttp denial of service via varint overflow in Binary HTTP parser

CVE-2026-61799Published November 19, 2026, updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 0.0.23.Final
Who is exposed
Not reported

Summary

The netty-incubator-codec-ohttp library's Binary HTTP parser mishandles large variable-length integers, which can wrap an internal offset and crash the decoder. A remote attacker without logging in can send a small malformed message with a large encoded length to repeatedly close the connection and cause 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 in codec-bhttp/src/main/java/io/netty/incubator/codec/bhttp/BinaryHttpParser.java accumulates attacker-controlled Binary HTTP variable-length integers into the int offset sumBytes. BinaryHttpParser.readRequestHead, BinaryHttpParser.readFieldLine, and BinaryHttpParser.getIndeterminateLength can narrow long lengths into that offset, causing integer wraparound before buffer indices are calculated. A remote peer that supplies a valid large encoded length to BinaryHttpParser or BinaryHttpDecoder can trigger an unchecked bounds exception from a small malformed message, fail or close the channel, and repeatedly cause denial of service. Java and Netty bounds checks prevent memory corruption, and no information disclosure was observed. This issue is fixed in version 0.0.23.Final.

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-61799 (netty-incubator-codec-ohttp: Binary HTTP parser unchecked varint length overflow causes decoder crash), 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-61799 (entry last updated 2026-11-19):
Affected:
- netty netty-incubator-codec-ohttp: fixed in 0.0.23.Final
Fixed versions: 0.0.23.Final.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-61799 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-61799 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-pgrf-4654-3gq8
- https://github.com/netty/netty-incubator-codec-ohttp/commit/a8d4909d3ecbf3101dcaa3d7136e2508ce0cde6e
- 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-61799
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-61799"}.

Affected versions

cve.now Index

22Pof 100 · provisional · methodology v3
  • 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

  1. CVE published
  2. First seen by cve.now

Evidence 5

Questions about CVE-2026-61799

Is CVE-2026-61799 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-61799?

netty-incubator-codec-ohttp: before 0.0.23.Final.

Source: cve.now feed data

How do I fix CVE-2026-61799?

Upgrade to a fixed version: 0.0.23.Final.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.