Is org.jboss.netty:netty 3.2 vulnerable?
Maven · 11 releases from 3.2.0 to 3.2.10 · latest org.jboss.netty:netty is 3.2.10.Final · checked 18 Nov 2026
Yes: 9 known advisories
Yes. org.jboss.netty:netty 3.2.10, the last 3.2 release, is affected by 9 known security advisories (1 critical, 3 high, 5 medium), including CVE-2019-20444, CVE-2021-37137, CVE-2021-37136. 1 more affects earlier 3.2.x releases. At least one has no fixed release yet.
Is your project on an affected org.jboss.netty:netty?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.jboss.netty:netty 3.2.10
HTTP request smuggling in netty
- Affected
- All versions
- Fixed in
- No fix released
SnappyFrameDecoder doesn't restrict chunk length any may buffer skippable chunks in an unnecessary way
- Affected
- All versions
- Fixed in
- No fix released
Bzip2Decoder doesn't allow setting size restrictions for decompressed data
- Affected
- All versions
- Fixed in
- No fix released
Possible request smuggling in HTTP/2 due missing validation of content-length
- Affected
- All versions
- Fixed in
- No fix released
Possible request smuggling in HTTP/2 due missing validation
- Affected
- All versions
- Fixed in
- No fix released
Local Information Disclosure Vulnerability in Netty on Unix-Like systems
- Affected
- All versions
- Fixed in
- No fix released
Information Exposure in Netty
- Affected
- <3.9.8.Final · >=3.10.0 <3.10.3.Final
- Fixed in
- 3.9.8.Final, 3.10.3.Final
HTTP Request Smuggling in Netty
- Affected
- All versions
- Fixed in
- No fix released
HTTP Request Smuggling in Netty
- Affected
- All versions
- Fixed in
- No fix released
Fixed within 3.2.x, affecting earlier releases
HTTP Request Smuggling in Netty
- Affected
- <=3.2.9.Final
- Fixed in
- No fix released
Every org.jboss.netty:netty 3.2.x release
Affected: 3.2.0 to 3.2.10. Latest org.jboss.netty:netty: 3.2.10.Final.
| Version | Known advisories |
|---|---|
| org.jboss.netty:netty 3.2.10 | CVE-2021-43797, CVE-2021-37137, CVE-2021-37136, CVE-2021-21409, CVE-2021-21295, CVE-2021-21290, CVE-2015-2156, CVE-2019-20444, CVE-2019-20445 |
| org.jboss.netty:netty 3.2.9 | CVE-2021-43797, CVE-2021-37137, CVE-2021-37136, CVE-2021-21409, CVE-2021-21295, CVE-2021-21290, CVE-2015-2156, CVE-2019-20444, CVE-2019-20445, CVE-2019-16869 |
| org.jboss.netty:netty 3.2.8 | CVE-2021-43797, CVE-2021-37137, CVE-2021-37136, CVE-2021-21409, CVE-2021-21295, CVE-2021-21290, CVE-2015-2156, CVE-2019-20444, CVE-2019-20445, CVE-2019-16869 |
| org.jboss.netty:netty 3.2.7 | CVE-2021-43797, CVE-2021-37137, CVE-2021-37136, CVE-2021-21409, CVE-2021-21295, CVE-2021-21290, CVE-2015-2156, CVE-2019-20444, CVE-2019-20445, CVE-2019-16869 |
| org.jboss.netty:netty 3.2.6 | CVE-2021-43797, CVE-2021-37137, CVE-2021-37136, CVE-2021-21409, CVE-2021-21295, CVE-2021-21290, CVE-2015-2156, CVE-2019-20444, CVE-2019-20445, CVE-2019-16869 |
| org.jboss.netty:netty 3.2.5 | CVE-2021-43797, CVE-2021-37137, CVE-2021-37136, CVE-2021-21409, CVE-2021-21295, CVE-2021-21290, CVE-2015-2156, CVE-2019-20444, CVE-2019-20445, CVE-2019-16869 |
| org.jboss.netty:netty 3.2.4 | CVE-2021-43797, CVE-2021-37137, CVE-2021-37136, CVE-2021-21409, CVE-2021-21295, CVE-2021-21290, CVE-2015-2156, CVE-2019-20444, CVE-2019-20445, CVE-2019-16869 |
| org.jboss.netty:netty 3.2.3 | CVE-2021-43797, CVE-2021-37137, CVE-2021-37136, CVE-2021-21409, CVE-2021-21295, CVE-2021-21290, CVE-2015-2156, CVE-2019-20444, CVE-2019-20445, CVE-2019-16869 |
| org.jboss.netty:netty 3.2.2 | CVE-2021-43797, CVE-2021-37137, CVE-2021-37136, CVE-2021-21409, CVE-2021-21295, CVE-2021-21290, CVE-2015-2156, CVE-2019-20444, CVE-2019-20445, CVE-2019-16869 |
| org.jboss.netty:netty 3.2.1 | CVE-2021-43797, CVE-2021-37137, CVE-2021-37136, CVE-2021-21409, CVE-2021-21295, CVE-2021-21290, CVE-2015-2156, CVE-2019-20444, CVE-2019-20445, CVE-2019-16869 |
| org.jboss.netty:netty 3.2.0 | CVE-2021-43797, CVE-2021-37137, CVE-2021-37136, CVE-2021-21409, CVE-2021-21295, CVE-2021-21290, CVE-2015-2156, CVE-2019-20444, CVE-2019-20445, CVE-2019-16869 |
Which of your client projects are still on org.jboss.netty:netty 3.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.jboss.netty:netty version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.jboss.netty:netty versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.