WaratekVRT Sign in

CVE-2026-61827

Severity8.7 High CVSS 4.0
Fixed in0.0.23.Final
WeaknessUncontrolled resource consumption (CWE-400)
Published19 Nov 2026

Not yet in NVD's feed. The description, CVSS score and weakness below come from the organisation that issued the CVE. NVD hasn't analysed it yet, and its NVD page may not exist yet.

Published yesterday. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The scope and status here may change.

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.

CWE-770

Exploitation status

No public exploit

No exploit has been reported in the sources we check.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment no assessment published
  • Indexed PoC none indexed
  • EPSS not scored

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: netty/netty-incubator-codec-ohttp c5169de.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.
Candidate fix https://github.com/netty/netty-incubator-codec-ohttp/commit/c5169de8814dbe730280fd793a0428a844e9045c : a commit: the change itself

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
io.netty.incubator:netty-incubator-codec-bhttp 0 0.0.23.Final unbounded

Products and versions

1 product, 1 version entry
SourceVendorProductSchemeAffected versions
osv io.netty.incubator netty-incubator-codec-bhttp generic < 0.0.23

References

URLTags
https://github.com/netty/netty-incubator-codec-ohttp/commit/c5169de8814dbe730280fd793a0428a844e9045c commit
https://github.com/netty/netty-incubator-codec-ohttp/security/advisories/GHSA-hmq9-67w8-j5pw WEB
https://github.com/netty/netty-incubator-codec-ohttp PACKAGE
https://github.com/netty/netty-incubator-codec-ohttp/releases/tag/netty-incubator-codec-parent-ohttp-0.0.23.Final WEB

Timeline

Published2026-11-19By the CVE Program.
NVD record modified2026-11-19NVD's own last-modified date for this record.