netty-incubator-codec-ohttp: Binary HTTP parser unchecked varint length overflow causes decoder crash

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary io.netty.incubator:netty-incubator-codec-bhttp uses attacker-controlled Binary HTTP variable-length integers as long values but accumulates them into int offsets. Large valid varint lengths wrap the internal offset negative, leading to unchecked ArrayIndexOutOfBoundsException / IndexOutOfBoundsException from a tiny malformed BHTTP payload. A remote peer can trigger connection-level denial of service in applications that expose BinaryHttpParser / BinaryHttpDecoder to untrusted input. Details In codec-bhttp/src/main/java/io/netty/incubator/codec/bhttp/BinaryHttpParser.java, several parser paths store cumulative byte offsets in int sumBytes and then add attacker-controlled long lengths using compound assignment. In Java, int += long narrows the result back to int, so a length such as 2^31 wraps sumBytes negative. Primary request-control-data path: - readRequestHead(...) declares int sumBytes = 0 at BinaryHttpParser.java:386. - It reads methodLength as a long at…

Published by the source

20 Aug 2026, 18:43 UTC

Last modified by the source

20 Aug 2026, 19:11 UTC

Source last checked

26 Oct 2026, 16:54 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-pgrf-4654-3gq8

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-pgrf-4654-3gq8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61799

Advisory: netty-incubator-codec-ohttp: Binary HTTP parser unchecked varint length overflow causes decoder crash
IDs: CVE-2026-61799, GHSA-pgrf-4654-3gq8
Record: https://patchnext.com/advisories/cve-2026-61799 (revision 2, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.netty.incubator:netty-incubator-codec-bhttp 0.0.23.Final. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.netty.incubator:netty-incubator-codec-bhttp: affected <= 0.0.22.Final; fixed in 0.0.23.Final

## Suggested inspection (read-only)
- Maven io.netty.incubator:netty-incubator-codec-bhttp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.netty.incubator:netty-incubator-codec-bhttp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-pgrf-4654-3gq8 (OSV record GHSA-pgrf-4654-3gq8 lists affected ranges: Maven io.netty.incubator:netty-incubator-codec-bhttp >=0 <0.0.23.Final (fixed))
- Verified: https://github.com/advisories/GHSA-pgrf-4654-3gq8 (GitHub-reviewed advisory GHSA-pgrf-4654-3gq8 lists affected ranges: Maven io.netty.incubator:netty-incubator-codec-bhttp >=0 <=0.0.22.Final)

Commands are suggestions: review each one before running it.