Skip to main content
VulnerabilityPublished

CVE-2026-69133: netty-incubator-codec-ohttp · Missing Release of Resource after Effective Lifetime

Affects netty-incubator-codec-ohttpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.0.27.Final when convenient.

Data as of 19 Nov 2026, 21:52 UTC

CVSS 3.1 base score
5.3Medium
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.15.3
Patch
Available – fixed in 0.0.27.Final
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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.27.Final.

Affected software

ProductAffectedFixed in
nettynetty-incubator-codec-ohttpAffected
  • >=0.0.20.Final <0.0.27.Final
Fixed in
  • 0.0.27.Final

AI-suggested

Upgrade to netty-incubator-codec-ohttp version 0.0.27.Final or later, where the issue is fixed. No other mitigation is required as the fix addresses the resource release problem.

Description

A resource release issue exists in netty-incubator-codec-ohttp versions from 0.0.20.Final up to but not including 0.0.27.Final. The OHttpClientCodec and OHttpServerCodec components retain the outer cumulation buffer after an OHTTP exchange completes, causing memory to be held unnecessarily during long-lived idle keep-alive connections. This can lead to increased memory usage and availability pressure. The issue is fixed in version 0.0.27.Final.

References

Community reviews

Loading reviews…