cve.bz

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

5.3 mediumFix available

Medium (5.3) in netty netty-incubator-codec-ohttp. Fixed in io.netty.incubator:netty-incubator-codec-bhttp 0.0.23.Final.

On this page
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.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CWEs
CWE-190 Integer Overflow or Wraparound (Year 2038 problem, Y2K38, Y2038, Epochalypse)
CWE-248 Uncaught Exception
CWE-681 Incorrect Conversion between Numeric Types
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
Assigned by
GitHub_M (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • io.netty.incubator:netty-incubator-codec-bhttp (Maven): fixed in 0.0.23.Final

Ask an AI about this CVE

Show the promptExplain CVE-2026-61799 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61799?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61799?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-61799 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
netty-incubator-codec-ohttp< 0.0.23.Final

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-pgrf-4654-3gq8Mavenio.netty.incubator:netty-incubator-codec-bhttp<0.0.23.Final0.0.23.Final

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON