VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

ch.qos.logback:logback-classic: vulnerability history, versions and safety

ch.qos.logback:logback-classic is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 22 releases, from Jun 2021 to Nov 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 H1
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 ch.qos.logback:logback-classic vulnerabilities

Vulert verdict on ch.qos.logback:logback-classic 1.6.5 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 1.6.5 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 29 Nov 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 626 packages i
  • Stars 3,235 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence EPL-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 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 ch.qos.logback:logback-classic, 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
1.6.5 30 Sep 2026 none EPL-2.0 — Details →
1.6.4 24 Sep 2026 none EPL-2.0 — Details →
1.6.3 14 Aug 2026 none EPL-2.0 — Details →
1.6.2 11 Aug 2026 none EPL-2.0 — Details →
1.6.1 28 Jul 2026 none EPL-2.0 — Details →
1.6.0 23 Jul 2026 none EPL-2.0 — Details →
1.5.38 09 Jul 2026 none EPL-2.0 — Details →
1.5.37 26 Jun 2026 none EPL-2.0 — Details →
1.5.36 25 Jun 2026 none EPL-2.0 — Details →
1.5.35 23 Jun 2026 none EPL-2.0 — Details →
1.5.34 01 Jun 2026 none EPL-2.0 — Details →
1.5.33 27 May 2026 none EPL-2.0 — Details →
1.5.32 16 Feb 2026 none non-standard — Details →
1.5.31 14 Feb 2026 none non-standard — Details →
1.5.30 14 Feb 2026 none non-standard — Details →
1.5.29 09 Feb 2026 none non-standard — Details →
1.5.28 06 Feb 2026 none non-standard — Details →
1.5.27 30 Jan 2026 none non-standard — Details →
1.5.26 25 Jan 2026 none non-standard — Details →
1.5.25 17 Jan 2026 none non-standard — Details →
1.5.24 06 Jan 2026 none non-standard — Details →
1.5.23 21 Dec 2025 none non-standard — Details →
1.5.22 11 Dec 2025 none non-standard — Details →
1.5.21 10 Nov 2025 none non-standard — Details →
1.3.16 29 Oct 2025 none non-standard — Details →
1.5.20 19 Oct 2025 none non-standard — Details →
1.5.19 30 Sep 2025 none non-standard — Details →
1.5.18 18 Mar 2025 none non-standard — Details →
1.5.17 25 Feb 2025 none non-standard — Details →
1.5.16 05 Jan 2025 none non-standard — Details →
1.3.15 28 Dec 2024 none non-standard — Details →
1.5.15 21 Dec 2024 none non-standard — Details →
1.5.14 19 Dec 2024 none non-standard — Details →
1.5.13 18 Dec 2024 none non-standard — Details →
1.5.12 25 Oct 2024 none non-standard — Details →
1.5.11 15 Oct 2024 none non-standard — Details →
1.5.10 12 Oct 2024 none non-standard — Details →
1.5.9 08 Oct 2024 none non-standard — Details →
1.5.8 06 Sep 2024 none non-standard — Details →
1.5.7 15 Aug 2024 none non-standard — Details →
1.5.6 17 Apr 2024 none non-standard — Details →
1.5.5 12 Apr 2024 none non-standard — Details →
1.5.4 09 Apr 2024 none non-standard — Details →
1.5.3 04 Mar 2024 none non-standard — Details →
1.5.2 02 Mar 2024 none non-standard — Details →
1.5.1 28 Feb 2024 none non-standard — Details →
1.5.0 16 Feb 2024 none non-standard — Details →
1.2.13 01 Dec 2023 none non-standard — Details →
1.3.14 01 Dec 2023 none non-standard — Details →
1.4.14 01 Dec 2023 none non-standard — Details →
1.4.13 28 Nov 2023 none non-standard — Details →
1.3.13 28 Nov 2023 none non-standard — Details →
1.3.12 27 Nov 2023 none non-standard — Details →
1.4.12 27 Nov 2023 none non-standard — Details →
1.3.11 09 Aug 2023 H1 non-standard Yes Details →
1.4.11 09 Aug 2023 none non-standard — Details →
1.3.10 09 Aug 2023 H1 non-standard Yes Details →
1.4.10 09 Aug 2023 none non-standard — Details →
1.3.9 04 Aug 2023 H1 non-standard Yes Details →
1.4.9 04 Aug 2023 none non-standard — Details →
1.3.8 13 Jun 2023 H1 non-standard Yes Details →
1.4.8 13 Jun 2023 none non-standard — Details →
1.3.7 19 Apr 2023 H1 non-standard Yes Details →
1.4.7 19 Apr 2023 none non-standard — Details →
1.2.12 23 Mar 2023 none non-standard — Details →
1.3.6 15 Mar 2023 H1 non-standard Yes Details →
1.4.6 15 Mar 2023 none non-standard — Details →
1.3.5 18 Nov 2022 H1 non-standard Yes Details →
1.4.5 18 Nov 2022 none non-standard — Details →
1.4.4 10 Oct 2022 none non-standard — Details →
1.3.4 07 Oct 2022 H1 non-standard Yes Details →
1.3.3 02 Oct 2022 H1 non-standard Yes Details →
1.4.3 02 Oct 2022 none non-standard — Details →
1.3.2 02 Oct 2022 H1 non-standard Yes Details →
1.4.2 02 Oct 2022 none non-standard — Details →
1.4.1 14 Sep 2022 none non-standard — Details →
1.3.1 14 Sep 2022 H1 non-standard Yes Details →
1.3.0 28 Aug 2022 H1 non-standard Yes Details →
1.4.0 28 Aug 2022 none non-standard — Details →
1.3.0-beta0 09 Aug 2022 none non-standard — Details →
1.3.0-alpha16 19 May 2022 none non-standard — Details →
1.3.0-alpha15 09 May 2022 none non-standard — Details →
1.2.11 05 Mar 2022 none non-standard — Details →
1.3.0-alpha14 11 Feb 2022 none non-standard — Details →
1.3.0-alpha13 31 Jan 2022 none non-standard — Details →
1.2.10 23 Dec 2021 none non-standard — Details →
1.3.0-alpha12 22 Dec 2021 none non-standard — Details →
1.2.9 17 Dec 2021 none non-standard — Details →
1.3.0-alpha11 16 Dec 2021 none non-standard — Details →
1.2.8 14 Dec 2021 none non-standard — Details →
1.2.7 11 Nov 2021 none non-standard — Details →
1.2.6 09 Sep 2021 none non-standard — Details →
1.3.0-alpha10 23 Aug 2021 none non-standard — Details →
1.3.0-alpha9 13 Aug 2021 none non-standard — Details →
1.3.0-alpha8 12 Aug 2021 none non-standard — Details →
1.3.0-alpha7 10 Aug 2021 none non-standard — Details →
1.3.0-alpha6 28 Jul 2021 none non-standard — Details →
1.2.5 26 Jul 2021 none non-standard — Details →
1.2.4-groovyless 22 Jul 2021 none non-standard — Details →
1.2.4 19 Jul 2021 none non-standard — Details →
1.3.0-alpha5 22 Oct 2019 none — — Details →
1.3.0-alpha4 11 Feb 2018 none — — Details →
1.3.0-alpha3 10 Feb 2018 none — — Details →
1.3.0-alpha2 30 Jan 2018 none — — Details →
1.3.0-alpha1 29 Jan 2018 none — — Details →
1.3.0-alpha0 18 Jan 2018 none — — Details →
1.2.3 31 Mar 2017 none — — Details →
1.2.2 16 Mar 2017 none — — Details →
1.1.11 01 Mar 2017 C1 — Yes Details →
1.2.1 09 Feb 2017 none — — Details →
1.2.0 08 Feb 2017 none — — Details →
1.1.10 05 Feb 2017 C1 — Yes Details →
1.1.9 20 Jan 2017 C1 — Yes Details →
1.1.8 09 Dec 2016 C1 — Yes Details →
1.1.7 29 Mar 2016 C1 — Yes Details →
1.1.6 29 Feb 2016 C1 — Yes Details →
1.1.5 13 Feb 2016 C1 — Yes Details →
1.1.4 11 Feb 2016 C1 — Yes Details →
1.1.3 24 Mar 2015 C1 — Yes Details →
1.1.2 02 Apr 2014 C1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2023 1

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

03 Vulnerabilities

Recorded vulnerabilities for ch.qos.logback:logback-classic

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-5929: QOS.ch Logback Serialization Vulnerability 9.8 critical 1.2.0 07 Jun 2021
CVE-2023-6378: logback serialization vulnerability 7.1 high 1.3.12 29 Nov 2023

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 ch.qos.logback:logback-classic

Is ch.qos.logback:logback-classic safe to use?

Vulert records 2 vulnerabilities for ch.qos.logback:logback-classic in Maven: 1 critical, 1 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 ch.qos.logback:logback-classic's Vulert package health score?

Vulert scores ch.qos.logback:logback-classic 82/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 ch.qos.logback:logback-classic affected?

No. 1.6.5, 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 ch.qos.logback:logback-classic should I use?

1.6.5 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 ch.qos.logback:logback-classic have?

2 vulnerabilities are recorded for ch.qos.logback:logback-classic in the Maven ecosystem: 1 critical, 1 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 ch.qos.logback:logback-classic vulnerabilities disclosed?

0 vulnerabilities were recorded for ch.qos.logback:logback-classic in the last 12 months, and the oldest entry in this database dates to 07 Jun 2021. 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 ch.qos.logback:logback-classic 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 ch.qos.logback:logback-classic for upcoming vulnerabilities?

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