VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

io.netty:netty-handler: vulnerability history, versions and safety

io.netty:netty-handler is a package in the Maven ecosystem. Vulert records 14 vulnerabilities for it across 120 releases, from Feb 2020 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded C1 H8 M5
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
5 in the last 12 months

Most recent disclosure 08 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all io.netty:netty-handler vulnerabilities

Vulert verdict on io.netty:netty-handler 5.0.0.Alpha2 i

Updated on 23 Oct 2026

Careful: 5.0.0.Alpha2 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Widely used
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 5.0.0.Alpha2 — affected i
  • Vulnerabilities on record 14 over 6 years · 5 in the last year i
  • Latest disclosure 08 Sep 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 1 i
  • Depended on by 30 packages i
  • Stars 35,061 i
  • OpenSSF scorecard 7/10 i
  • Last release 139 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for io.netty:netty-handler, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.1.139.Final 06 Oct 2026 M1 Apache-2.0 No Details →
4.2.19.Final 06 Oct 2026 M1 Apache-2.0 No Details →
4.1.138.Final 09 Sep 2026 M1 Apache-2.0 No Details →
4.2.18.Final 09 Sep 2026 M1 Apache-2.0 No Details →
4.1.137.Final 06 Aug 2026 M1 Apache-2.0 No Details →
4.2.17.Final 04 Aug 2026 M1 Apache-2.0 No Details →
4.1.136.Final 08 Jul 2026 M1 Apache-2.0 No Details →
4.2.16.Final 07 Jul 2026 C1 M1 Apache-2.0 Yes Details →
4.1.135.Final 02 Jun 2026 M1 Apache-2.0 No Details →
4.2.15.Final 02 Jun 2026 C1 M1 Apache-2.0 Yes Details →
4.1.134.Final 20 May 2026 M1 Apache-2.0 No Details →
4.2.14.Final 20 May 2026 C1 H3 M1 Apache-2.0 Yes Details →
4.1.133.Final 05 May 2026 M1 Apache-2.0 No Details →
4.2.13.Final 04 May 2026 C1 H3 M1 Apache-2.0 Yes Details →
4.2.12.Final 25 Mar 2026 C1 H3 M1 Apache-2.0 Yes Details →
4.1.132.Final 24 Mar 2026 M1 Apache-2.0 No Details →
4.2.11.Final 24 Mar 2026 C1 H3 M1 Apache-2.0 Yes Details →
4.1.131.Final 05 Feb 2026 M1 Apache-2.0 No Details →
4.2.10.Final 05 Feb 2026 C1 H3 M1 Apache-2.0 Yes Details →
4.2.9.Final 15 Dec 2025 C1 H3 M1 Apache-2.0 Yes Details →
4.1.130.Final 15 Dec 2025 M1 Apache-2.0 No Details →
4.2.8.Final 11 Dec 2025 C1 H3 M1 Apache-2.0 Yes Details →
4.1.129.Final 11 Dec 2025 M1 Apache-2.0 No Details →
4.1.128.Final 14 Oct 2025 M1 Apache-2.0 No Details →
4.2.7.Final 14 Oct 2025 C1 H3 M1 Apache-2.0 Yes Details →
4.2.6.Final 08 Sep 2025 C1 H3 M1 Apache-2.0 Yes Details →
4.1.127.Final 08 Sep 2025 M1 Apache-2.0 No Details →
4.2.5.Final 03 Sep 2025 C1 H3 M1 Apache-2.0 Yes Details →
4.1.126.Final 03 Sep 2025 M1 Apache-2.0 No Details →
4.1.125.Final 03 Sep 2025 M1 Apache-2.0 No Details →
4.2.4.Final 13 Aug 2025 C1 H3 M1 Apache-2.0 Yes Details →
4.1.124.Final 13 Aug 2025 M1 Apache-2.0 No Details →
4.1.123.Final 15 Jul 2025 M1 Apache-2.0 No Details →
4.2.3.Final 14 Jul 2025 C1 H3 M1 Apache-2.0 Yes Details →
4.2.2.Final 05 Jun 2025 C1 H3 M1 Apache-2.0 Yes Details →
4.1.122.Final 03 Jun 2025 M1 Apache-2.0 No Details →
4.2.1.Final 06 May 2025 C1 H3 M1 Apache-2.0 Yes Details →
4.1.121.Final 24 Apr 2025 M1 Apache-2.0 No Details →
4.1.120.Final 23 Apr 2025 M1 Apache-2.0 No Details →
4.2.0.Final 03 Apr 2025 C1 H3 M1 Apache-2.0 Yes Details →
4.2.0.RC4 08 Mar 2025 C1 H3 M2 Apache-2.0 No Details →
4.1.119.Final 26 Feb 2025 M1 Apache-2.0 No Details →
4.2.0.RC3 11 Feb 2025 C1 H3 M2 Apache-2.0 No Details →
4.1.118.Final 10 Feb 2025 M1 Apache-2.0 No Details →
4.2.0.RC2 20 Jan 2025 C1 H3 M2 Apache-2.0 No Details →
4.1.117.Final 14 Jan 2025 H2 Apache-2.0 Yes Details →
4.1.116.Final 17 Dec 2024 H2 Apache-2.0 Yes Details →
4.2.0.RC1 10 Dec 2024 C1 H3 M2 Apache-2.0 No Details →
4.1.115.Final 12 Nov 2024 H2 Apache-2.0 Yes Details →
4.2.0.Beta1 04 Nov 2024 C1 H3 M2 Apache-2.0 No Details →
4.2.0.Alpha5 09 Oct 2024 C1 H3 M2 Apache-2.0 No Details →
4.1.114.Final 01 Oct 2024 H2 Apache-2.0 Yes Details →
4.2.0.Alpha4 05 Sep 2024 C1 H3 M2 Apache-2.0 No Details →
4.1.113.Final 04 Sep 2024 H2 Apache-2.0 Yes Details →
4.2.0.Alpha3 26 Aug 2024 C1 H3 M2 Apache-2.0 No Details →
4.1.112.Final 19 Jul 2024 H2 Apache-2.0 Yes Details →
4.2.0.Alpha2 03 Jul 2024 C1 H3 M2 Apache-2.0 No Details →
4.2.0.Alpha1 12 Jun 2024 C1 H3 M2 Apache-2.0 No Details →
4.1.111.Final 11 Jun 2024 H2 Apache-2.0 Yes Details →
4.1.110.Final 22 May 2024 H2 Apache-2.0 Yes Details →
4.1.109.Final 15 Apr 2024 H2 Apache-2.0 Yes Details →
4.1.108.Final 21 Mar 2024 H2 Apache-2.0 Yes Details →
4.1.107.Final 13 Feb 2024 H2 Apache-2.0 Yes Details →
4.1.106.Final 19 Jan 2024 H2 Apache-2.0 Yes Details →
4.1.105.Final 16 Jan 2024 H2 Apache-2.0 Yes Details →
4.1.104.Final 15 Dec 2023 H2 Apache-2.0 Yes Details →
4.1.103.Final 13 Dec 2023 H2 Apache-2.0 Yes Details →
4.1.102.Final 12 Dec 2023 H2 Apache-2.0 Yes Details →
4.1.101.Final 09 Nov 2023 H2 Apache-2.0 Yes Details →
4.1.100.Final 10 Oct 2023 H2 Apache-2.0 Yes Details →
4.1.99.Final 28 Sep 2023 H2 M1 Apache-2.0 No Details →
4.1.98.Final 21 Sep 2023 H2 M1 Apache-2.0 No Details →
4.1.97.Final 23 Aug 2023 H2 M1 Apache-2.0 No Details →
4.1.96.Final 27 Jul 2023 H2 M1 Apache-2.0 No Details →
4.1.95.Final 20 Jul 2023 H2 M1 Apache-2.0 No Details →
4.1.94.Final 20 Jun 2023 H2 M1 Apache-2.0 No Details →
4.1.93.Final 25 May 2023 H2 M2 Apache-2.0 No Details →
4.1.92.Final 25 Apr 2023 H2 M2 Apache-2.0 No Details →
4.1.91.Final 03 Apr 2023 H2 M2 Apache-2.0 No Details →
4.1.90.Final 14 Mar 2023 M2 Apache-2.0 No Details →
4.1.89.Final 13 Feb 2023 M2 Apache-2.0 No Details →
4.1.88.Final 12 Feb 2023 M2 Apache-2.0 No Details →
4.1.87.Final 12 Jan 2023 M2 Apache-2.0 No Details →
4.1.86.Final 12 Dec 2022 M2 Apache-2.0 No Details →
4.1.85.Final 09 Nov 2022 M2 Apache-2.0 No Details →
4.1.84.Final 12 Oct 2022 M2 Apache-2.0 No Details →
4.1.83.Final 11 Oct 2022 M2 Apache-2.0 No Details →
4.1.82.Final 13 Sep 2022 M2 Apache-2.0 No Details →
4.1.81.Final 08 Sep 2022 M2 Apache-2.0 No Details →
4.1.80.Final 26 Aug 2022 M2 Apache-2.0 No Details →
4.1.79.Final 11 Jul 2022 M2 Apache-2.0 No Details →
4.1.78.Final 14 Jun 2022 M2 Apache-2.0 No Details →
4.1.77.Final 06 May 2022 M2 Apache-2.0 No Details →
4.1.76.Final 12 Apr 2022 M2 Apache-2.0 No Details →
4.1.75.Final 10 Mar 2022 M2 Apache-2.0 No Details →
4.1.74.Final 08 Feb 2022 M2 Apache-2.0 No Details →
4.1.73.Final 12 Jan 2022 M2 Apache-2.0 No Details →
4.1.72.Final 13 Dec 2021 M2 Apache-2.0 No Details →
4.1.71.Final 09 Dec 2021 M2 Apache-2.0 No Details →
4.1.70.Final 03 Nov 2021 M2 Apache-2.0 No Details →
4.1.69.Final 11 Oct 2021 M2 — No Details →
4.1.68.Final 09 Sep 2021 M2 — No Details →
4.1.67.Final 16 Aug 2021 M2 — No Details →
4.1.66.Final 16 Jul 2021 M2 — No Details →
4.1.65.Final 19 May 2021 M2 — No Details →
4.1.64.Final 17 May 2021 M2 — No Details →
4.1.63.Final 01 Apr 2021 M2 — No Details →
4.1.62.Final 30 Mar 2021 M2 — No Details →
4.1.61.Final 30 Mar 2021 M2 — No Details →
4.1.60.Final 09 Mar 2021 M2 — No Details →
4.1.59.Final 08 Feb 2021 M2 — No Details →
4.1.58.Final 13 Jan 2021 M2 — No Details →
4.1.57.Final 12 Jan 2021 M2 — No Details →
4.1.56.Final 17 Dec 2020 M2 — No Details →
4.1.55.Final 08 Dec 2020 M2 — No Details →
4.1.54.Final 11 Nov 2020 M2 — No Details →
4.1.53.Final 13 Oct 2020 M2 — No Details →
4.1.52.Final 08 Sep 2020 M2 — No Details →
4.1.51.Final 09 Jul 2020 M2 — No Details →
4.1.50.Final 13 May 2020 M2 — No Details →

The newest 120 of 265 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 4
  • 2022 1
  • 2023 2
  • 2025 2
  • 2026 5

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 5 of the 14 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for io.netty:netty-handler

The 5 most severe of 14 vulnerabilities recorded for this package

Search all 14 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-75595: Netty SNI Routing Bypass via Fragmented TLS ClientHello 9.1 critical 4.2.17.Final 08 Sep 2026
CVE-2026-44249: Netty Handler IPv6 Subnet Filter Bypass Vulnerability 8.1 high 4.2.15.Final 08 Jun 2026
CVE-2020-7238: HTTP Request Smuggling in Netty 7.5 high 4.1.45 21 Feb 2020
CVE-2025-24970: High Severity Vulnerability in io.netty:netty-handler Leading to Native Crash 7.5 high 4.1.118.Final 10 Feb 2025
CVE-2025-24970: Vulnerability in io.netty:netty-handler Leading to Native Crash 7.5 high 4.1.118.Final 10 Feb 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About io.netty:netty-handler

Is io.netty:netty-handler safe to use?

Vulert records 14 vulnerabilities for io.netty:netty-handler in Maven: 1 critical, 8 high, 5 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is io.netty:netty-handler's Vulert package health score?

Vulert scores io.netty:netty-handler 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of io.netty:netty-handler affected?

Yes. 5.0.0.Alpha2, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of io.netty:netty-handler should I use?

5.0.0.Alpha2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does io.netty:netty-handler have?

14 vulnerabilities are recorded for io.netty:netty-handler in the Maven ecosystem: 1 critical, 8 high, 5 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new io.netty:netty-handler vulnerabilities disclosed?

5 vulnerabilities were recorded for io.netty:netty-handler in the last 12 months, and the oldest entry in this database dates to 21 Feb 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of io.netty:netty-handler are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor io.netty:netty-handler for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the io.netty:netty-handler version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.