Skip to main content
VulnerabilityPublished

CVE-2026-63202: netty-incubator-codec-ohttp · Uncontrolled Resource Consumption

Affects netty-incubator-codec-ohttpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 0.0.23.Final soon.

Data as of 19 Nov 2026, 21:52 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.5
Patch
Available – fixed in 0.0.23.Final
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade netty-incubator-codec-ohttp to 0.0.23.Final.

Affected software

ProductAffectedFixed in
nettynetty-incubator-codec-ohttpAffected
  • <0.0.23.Final
Fixed in
  • 0.0.23.Final

AI-suggested

Upgrade netty-incubator-codec-ohttp to version 0.0.23.Final or later, where this vulnerability is fixed. No other mitigations are indicated. Since this is not a cloud service, manual patching is required.

Description

CVE-2026-63202 is a high-severity vulnerability in netty-incubator-codec-ohttp prior to version 0.0.23.Final. It involves uncontrolled resource consumption due to improper handling of corrupted or truncated Binary HTTP field lines during parsing. An unauthenticated attacker can exploit this to cause a Netty event-loop thread to consume full CPU indefinitely, leading to denial of service by exhausting event-loop resources. The issue is fixed in version 0.0.23.Final.

References

Community reviews

Loading reviews…