Netty:
Affects nettySource GCVE Database
Not known to be exploited · CVSS 9.1 Critical · fixed in 4.1.136 : patch netty as a priority.
Data as of 9 Nov 2026, 14:17 UTC
- Patch
- Available – fixed in 4.1.136
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 9 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10nettypkg:deb/ubuntu/netty?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu Pro 26.04 LTSnettypkg:deb/ubuntu/netty?arch=source&distro=esm-apps/resoluteOther threats | Affected
| Fixed in– |
Ubuntu Pro 24.04 LTSnettypkg:deb/ubuntu/netty?arch=source&distro=esm-apps/nobleOther threats | Affected
| Fixed in– |
Ubuntu Pro 22.04 LTSnettypkg:deb/ubuntu/netty?arch=source&distro=esm-apps/jammyOther threats | Affected
| Fixed in– |
Ubuntu Pro 18.04 LTSnettypkg:deb/ubuntu/netty?arch=source&distro=esm-apps/bionicOther threats | Affected
| Fixed in– |
Ubuntu Pro 16.04 LTSnettypkg:deb/ubuntu/netty?arch=source&distro=esm-apps-legacy/xenialOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Netty to version 4.1.136.Final or later, or 4.2.16.Final or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory.
Description
Netty versions 4.2.0.Final through 4.2.15.Final and versions prior to 4.1.135.Final contain a vulnerability in the OcspClient component where it does not properly validate that the CertificateID in an OCSP response matches the requested CertificateID. This flaw allows an attacker to bypass revocation checks by replaying a legitimately signed 'GOOD' status response for a different certificate issued by the same CA. The issue is resolved in versions 4.1.136.Final and 4.2.16.Final.