VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

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

io.jooby:jooby-netty is a package in the Maven ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in Apr 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all io.jooby:jooby-netty vulnerabilities

Vulert verdict on io.jooby:jooby-netty 4.5.4 i

Updated on 22 Oct 2026

Good news: 4.5.4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Stay on 4.5.4 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.5.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.5.4 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 03 Apr 2020 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Last release 2 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.jooby:jooby-netty, 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
3.12.0 07 Aug 2026 none Apache-2.0 — Details →
4.5.4 29 Jul 2026 none Apache-2.0 — Details →
3.11.10 29 Jul 2026 none Apache-2.0 — Details →
4.5.3 01 Jul 2026 none Apache-2.0 — Details →
3.11.9 17 Jun 2026 none Apache-2.0 — Details →
4.5.2 03 Jun 2026 none Apache-2.0 — Details →
4.5.1 12 May 2026 none Apache-2.0 — Details →
3.11.8 11 May 2026 none Apache-2.0 — Details →
4.5.0 07 May 2026 none Apache-2.0 — Details →
4.4.0 14 Apr 2026 none Apache-2.0 — Details →
4.3.0 08 Apr 2026 none Apache-2.0 — Details →
4.2.0 31 Mar 2026 none Apache-2.0 — Details →
4.1.0 16 Mar 2026 none Apache-2.0 — Details →
4.0.17 10 Mar 2026 none Apache-2.0 — Details →
3.11.7 10 Mar 2026 none Apache-2.0 — Details →
4.0.16 02 Mar 2026 none Apache-2.0 — Details →
3.11.6 14 Jan 2026 none Apache-2.0 — Details →
4.0.15 14 Jan 2026 none Apache-2.0 — Details →
4.0.14 13 Jan 2026 none Apache-2.0 — Details →
4.0.13 22 Dec 2025 none Apache-2.0 — Details →
4.0.12 26 Nov 2025 none Apache-2.0 — Details →
4.0.11 04 Nov 2025 none Apache-2.0 — Details →
4.0.10 27 Oct 2025 none Apache-2.0 — Details →
3.11.5 27 Oct 2025 none Apache-2.0 — Details →
4.0.9 20 Oct 2025 none Apache-2.0 — Details →
4.0.8 20 Oct 2025 none Apache-2.0 — Details →
3.11.4 20 Oct 2025 none Apache-2.0 — Details →
3.11.3 14 Oct 2025 none Apache-2.0 — Details →
4.0.7 08 Sep 2025 none Apache-2.0 — Details →
4.0.6 13 Aug 2025 none Apache-2.0 — Details →
4.0.5 07 Aug 2025 none Apache-2.0 — Details →
3.11.2 07 Aug 2025 none Apache-2.0 — Details →
4.0.4 05 Aug 2025 none Apache-2.0 — Details →
4.0.3 29 Jul 2025 none Apache-2.0 — Details →
3.11.1 29 Jul 2025 none Apache-2.0 — Details →
4.0.2 27 Jul 2025 none Apache-2.0 — Details →
4.0.1 25 Jul 2025 none Apache-2.0 — Details →
4.0.0 25 Jul 2025 none Apache-2.0 — Details →
3.11.0 21 Jul 2025 none Apache-2.0 — Details →
3.10.0 02 Jul 2025 none Apache-2.0 — Details →
3.9.1 29 May 2025 none Apache-2.0 — Details →
3.9.0 27 May 2025 none Apache-2.0 — Details →
3.8.1 12 May 2025 none Apache-2.0 — Details →
3.8.0 05 May 2025 none Apache-2.0 — Details →
3.7.0 31 Mar 2025 none Apache-2.0 — Details →
2.17.0 30 Mar 2025 none Apache-2.0 — Details →
3.6.1 13 Feb 2025 none Apache-2.0 — Details →
3.6.0 07 Jan 2025 none Apache-2.0 — Details →
3.5.5 09 Dec 2024 none Apache-2.0 — Details →
3.5.4 21 Nov 2024 none Apache-2.0 — Details →
3.5.3 14 Nov 2024 none Apache-2.0 — Details →
3.5.2 13 Nov 2024 none Apache-2.0 — Details →
3.5.1 07 Nov 2024 none Apache-2.0 — Details →
3.5.0 05 Nov 2024 none Apache-2.0 — Details →
3.4.3 28 Oct 2024 none Apache-2.0 — Details →
3.4.2 14 Oct 2024 none Apache-2.0 — Details →
3.4.1 23 Sep 2024 none Apache-2.0 — Details →
3.4.0 19 Sep 2024 none Apache-2.0 — Details →
3.3.1 09 Sep 2024 none Apache-2.0 — Details →
3.3.0 04 Sep 2024 none Apache-2.0 — Details →
3.2.9 15 Aug 2024 none Apache-2.0 — Details →
3.2.8 06 Aug 2024 none Apache-2.0 — Details →
3.2.7 29 Jul 2024 none Apache-2.0 — Details →
3.2.6 22 Jul 2024 none Apache-2.0 — Details →
3.2.5 16 Jul 2024 none Apache-2.0 — Details →
3.2.4 08 Jul 2024 none Apache-2.0 — Details →
3.2.3 24 Jun 2024 none Apache-2.0 — Details →
3.2.2 20 Jun 2024 none Apache-2.0 — Details →
3.1.4 20 Jun 2024 none Apache-2.0 — Details →
3.2.1 18 Jun 2024 none Apache-2.0 — Details →
3.2.0 10 Jun 2024 none Apache-2.0 — Details →
3.1.3 05 Jun 2024 none Apache-2.0 — Details →
2.16.4 05 Jun 2024 none Apache-2.0 — Details →
3.1.2 27 May 2024 none Apache-2.0 — Details →
3.1.1 20 May 2024 none Apache-2.0 — Details →
3.1.0 13 May 2024 none Apache-2.0 — Details →
3.0.10 16 Apr 2024 none Apache-2.0 — Details →
3.0.9 11 Mar 2024 none Apache-2.0 — Details →
3.0.8 27 Feb 2024 none Apache-2.0 — Details →
3.0.7 04 Jan 2024 none Apache-2.0 — Details →
2.16.3 28 Oct 2023 none Apache-2.0 — Details →
3.0.6 16 Oct 2023 none Apache-2.0 — Details →
3.0.5 28 Aug 2023 none Apache-2.0 — Details →
3.0.4 28 Aug 2023 none Apache-2.0 — Details →
3.0.3 21 Aug 2023 none Apache-2.0 — Details →
3.0.2 15 Aug 2023 none Apache-2.0 — Details →
3.0.1 31 Jul 2023 none Apache-2.0 — Details →
3.0.0 03 Jul 2023 none Apache-2.0 — Details →
3.0.0.M11 17 Jun 2023 none Apache-2.0 — Details →
3.0.0.M9 22 May 2023 none Apache-2.0 — Details →
3.0.0.M7 17 Apr 2023 none Apache-2.0 — Details →
3.0.0.M6 03 Apr 2023 none Apache-2.0 — Details →
3.0.0.M5 25 Mar 2023 none Apache-2.0 — Details →
3.0.0.M4 06 Mar 2023 none Apache-2.0 — Details →
3.0.0.M3 05 Mar 2023 none Apache-2.0 — Details →
2.16.2 04 Mar 2023 none Apache-2.0 — Details →
3.0.0.M2 01 Jan 2023 none Apache-2.0 — Details →
3.0.0.M1 05 Dec 2022 none Apache-2.0 — Details →
2.16.1 06 Sep 2022 none Apache-2.0 — Details →
2.16.0 06 Sep 2022 none Apache-2.0 — Details →
2.15.1 27 May 2022 none — — Details →
2.15.0 22 May 2022 none — — Details →
2.14.2 14 May 2022 none — — Details →
2.14.1 02 May 2022 none — — Details →
2.14.0 27 Apr 2022 none — — Details →
2.13.0 16 Jan 2022 none — — Details →
2.12.0 30 Dec 2021 none — — Details →
2.11.0 15 Sep 2021 none — — Details →
2.10.0 18 Jul 2021 none — — Details →
2.9.6 10 May 2021 none — — Details →
2.9.5 27 Dec 2020 none — — Details →
2.9.4 25 Nov 2020 none — — Details →
2.9.3 13 Nov 2020 none — — Details →
2.9.2 25 Oct 2020 none — — Details →
2.9.1 01 Oct 2020 none — — Details →
2.9.0 07 Sep 2020 none — — Details →
2.8.10 03 Aug 2020 none — — Details →
2.8.9 02 Jul 2020 none — — Details →
2.8.8 25 Jun 2020 none — — Details →
2.8.7 20 Jun 2020 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

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

03 Vulnerabilities

Recorded vulnerabilities for io.jooby:jooby-netty

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-7622: HTTP Response Splitting in Jooby ('HTTP Response Splitting) 9.8 critical 2.2.1 03 Apr 2020

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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.jooby:jooby-netty

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

Vulert records 1 vulnerabilities for io.jooby:jooby-netty in Maven: 1 critical, 0 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

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

Vulert scores io.jooby:jooby-netty 77/100, which reads as in good shape. 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).

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

No. 4.5.4, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

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

4.5.4 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.jooby:jooby-netty have?

1 vulnerability is recorded for io.jooby:jooby-netty in the Maven ecosystem: 1 critical, 0 high, 0 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.jooby:jooby-netty vulnerabilities disclosed?

0 vulnerabilities were recorded for io.jooby:jooby-netty in the last 12 months, and the oldest entry in this database dates to 03 Apr 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.jooby:jooby-netty 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.jooby:jooby-netty for upcoming vulnerabilities?

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