VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

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

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

i
8 vulnerabilities recorded H1 M3 L4
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 01 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ch.qos.logback:logback-core vulnerabilities

Vulert verdict on ch.qos.logback:logback-core 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 8.

Package health score 78/100
  • Security Some issues to review
  • 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 8 over 4 years · 3 in the last year i
  • Latest disclosure 01 Jun 2026 i
  • Highest CVSS 7.1 i
  • With no published fix 0 i
  • Depended on by 674 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 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 ch.qos.logback:logback-core, 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 L1 EPL-2.0 Yes Details →
1.5.33 27 May 2026 L1 EPL-2.0 Yes Details →
1.5.32 16 Feb 2026 L2 non-standard Yes Details →
1.5.31 14 Feb 2026 L2 non-standard Yes Details →
1.5.30 14 Feb 2026 L2 non-standard Yes Details →
1.5.29 09 Feb 2026 L2 non-standard Yes Details →
1.5.28 06 Feb 2026 L2 non-standard Yes Details →
1.5.27 30 Jan 2026 L2 non-standard Yes Details →
1.5.26 25 Jan 2026 L2 non-standard Yes Details →
1.5.25 17 Jan 2026 L2 non-standard Yes Details →
1.5.24 06 Jan 2026 L3 non-standard Yes Details →
1.5.23 21 Dec 2025 L3 non-standard Yes Details →
1.5.22 11 Dec 2025 L3 non-standard Yes Details →
1.5.21 10 Nov 2025 L3 non-standard Yes Details →
1.3.16 29 Oct 2025 L3 non-standard Yes Details →
1.5.20 19 Oct 2025 L3 non-standard Yes Details →
1.5.19 30 Sep 2025 L3 non-standard Yes Details →
1.5.18 18 Mar 2025 M1 L3 non-standard Yes Details →
1.5.17 25 Feb 2025 M1 L3 non-standard Yes Details →
1.5.16 05 Jan 2025 M1 L3 non-standard Yes Details →
1.3.15 28 Dec 2024 M1 L3 non-standard Yes Details →
1.5.15 21 Dec 2024 M1 L3 non-standard Yes Details →
1.5.14 19 Dec 2024 M1 L3 non-standard Yes Details →
1.5.13 18 Dec 2024 M1 L3 non-standard Yes Details →
1.5.12 25 Oct 2024 M2 L4 non-standard Yes Details →
1.5.11 15 Oct 2024 M2 L4 non-standard Yes Details →
1.5.10 12 Oct 2024 M2 L4 non-standard Yes Details →
1.5.9 08 Oct 2024 M2 L4 non-standard Yes Details →
1.5.8 06 Sep 2024 M2 L4 non-standard Yes Details →
1.5.7 15 Aug 2024 M2 L4 non-standard Yes Details →
1.5.6 17 Apr 2024 M2 L4 non-standard Yes Details →
1.5.5 12 Apr 2024 M2 L4 non-standard Yes Details →
1.5.4 09 Apr 2024 M2 L4 non-standard Yes Details →
1.5.3 04 Mar 2024 M2 L4 non-standard Yes Details →
1.5.2 02 Mar 2024 M2 L4 non-standard Yes Details →
1.5.1 28 Feb 2024 M2 L4 non-standard Yes Details →
1.5.0 16 Feb 2024 M2 L4 non-standard Yes Details →
1.2.13 01 Dec 2023 M1 L3 non-standard Yes Details →
1.3.14 01 Dec 2023 M1 L3 non-standard Yes Details →
1.4.14 01 Dec 2023 M2 L4 non-standard Yes Details →
1.4.13 28 Nov 2023 H1 M2 L4 non-standard Yes Details →
1.3.13 28 Nov 2023 M1 L3 non-standard Yes Details →
1.3.12 27 Nov 2023 M1 L3 non-standard Yes Details →
1.4.12 27 Nov 2023 M2 L4 non-standard Yes Details →
1.3.11 09 Aug 2023 M1 L3 non-standard Yes Details →
1.4.11 09 Aug 2023 M2 L4 non-standard Yes Details →
1.3.10 09 Aug 2023 M1 L3 non-standard Yes Details →
1.4.10 09 Aug 2023 M2 L4 non-standard Yes Details →
1.3.9 04 Aug 2023 M1 L3 non-standard Yes Details →
1.4.9 04 Aug 2023 M2 L4 non-standard Yes Details →
1.3.8 13 Jun 2023 M1 L3 non-standard Yes Details →
1.4.8 13 Jun 2023 M2 L4 non-standard Yes Details →
1.3.7 19 Apr 2023 M1 L3 non-standard Yes Details →
1.4.7 19 Apr 2023 M2 L4 non-standard Yes Details →
1.2.12 23 Mar 2023 M1 L3 non-standard Yes Details →
1.3.6 15 Mar 2023 M1 L3 non-standard Yes Details →
1.4.6 15 Mar 2023 M2 L4 non-standard Yes Details →
1.3.5 18 Nov 2022 M1 L3 non-standard Yes Details →
1.4.5 18 Nov 2022 M2 L4 non-standard Yes Details →
1.4.4 10 Oct 2022 M2 L4 non-standard Yes Details →
1.3.4 07 Oct 2022 M1 L3 non-standard Yes Details →
1.3.3 02 Oct 2022 M1 L3 non-standard Yes Details →
1.4.3 02 Oct 2022 M2 L4 non-standard Yes Details →
1.3.2 02 Oct 2022 M1 L3 non-standard Yes Details →
1.4.2 02 Oct 2022 M2 L4 non-standard Yes Details →
1.4.1 14 Sep 2022 M2 L4 non-standard Yes Details →
1.3.1 14 Sep 2022 M1 L3 non-standard Yes Details →
1.3.0 28 Aug 2022 M1 L3 non-standard Yes Details →
1.4.0 28 Aug 2022 M2 L4 non-standard Yes Details →
1.3.0-beta0 09 Aug 2022 M1 L3 non-standard Yes Details →
1.3.0-alpha16 19 May 2022 M1 L3 non-standard Yes Details →
1.3.0-alpha15 09 May 2022 M1 L3 non-standard Yes Details →
1.2.11 05 Mar 2022 M1 L3 non-standard Yes Details →
1.3.0-alpha14 11 Feb 2022 M1 L3 non-standard Yes Details →
1.3.0-alpha13 31 Jan 2022 M1 L3 non-standard Yes Details →
1.2.10 23 Dec 2021 M1 L3 non-standard Yes Details →
1.3.0-alpha12 22 Dec 2021 M1 L3 non-standard Yes Details →
1.2.9 17 Dec 2021 M1 L3 non-standard Yes Details →
1.3.0-alpha11 16 Dec 2021 M1 L3 non-standard Yes Details →
1.2.8 14 Dec 2021 M2 L3 non-standard Yes Details →
1.2.7 11 Nov 2021 M2 L3 non-standard Yes Details →
1.2.6 09 Sep 2021 M2 L3 non-standard Yes Details →
1.3.0-alpha10 23 Aug 2021 M1 L3 non-standard Yes Details →
1.3.0-alpha9 13 Aug 2021 M1 L3 non-standard Yes Details →
1.3.0-alpha8 12 Aug 2021 M1 L3 non-standard Yes Details →
1.3.0-alpha7 10 Aug 2021 M1 L3 non-standard Yes Details →
1.3.0-alpha6 28 Jul 2021 M1 L3 non-standard Yes Details →
1.2.5 26 Jul 2021 M2 L3 non-standard Yes Details →
1.2.4-groovyless 22 Jul 2021 M2 L3 non-standard Yes Details →
1.2.4 19 Jul 2021 M2 L3 non-standard Yes Details →
1.3.0-alpha5 22 Oct 2019 M1 L3 — Yes Details →
1.3.0-alpha4 11 Feb 2018 M1 L3 — Yes Details →
1.3.0-alpha3 10 Feb 2018 M1 L3 — Yes Details →
1.3.0-alpha2 30 Jan 2018 M1 L3 — Yes Details →
1.3.0-alpha1 29 Jan 2018 M1 L3 — Yes Details →
1.3.0-alpha0 18 Jan 2018 M1 L3 — Yes Details →
1.2.3 31 Mar 2017 M2 L3 — Yes Details →
1.2.2 16 Mar 2017 M2 L3 — Yes Details →
1.1.11 01 Mar 2017 M2 L3 — Yes Details →
1.2.1 09 Feb 2017 M2 L3 — Yes Details →
1.2.0 08 Feb 2017 M2 L3 — Yes Details →
1.1.10 05 Feb 2017 M2 L3 — Yes Details →
1.1.9 20 Jan 2017 M2 L3 — Yes Details →
1.1.8 09 Dec 2016 M2 L3 — Yes Details →
1.1.7 29 Mar 2016 M2 L3 — Yes Details →
1.1.6 29 Feb 2016 M2 L3 — Yes Details →
1.1.5 13 Feb 2016 M2 L3 — Yes Details →
1.1.4 11 Feb 2016 M2 L3 — Yes Details →
1.1.3 24 Mar 2015 M2 L3 — Yes Details →
1.1.2 02 Apr 2014 M2 L3 — 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
  • 2024 2
  • 2025 1
  • 2026 3

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

03 Vulnerabilities

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

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-6481: Logback Core Denial-Of-Service Vulnerability 7.1 high 1.4.14 04 Dec 2023
CVE-2021-42550: logback-core - Deserialization of Untrusted Data 6.6 medium 1.2.9 17 Dec 2021
CVE-2024-12798: QOS.CH logback-core Expression Language Injection Vulnerability 5.9 medium 1.5.13 19 Dec 2024
CVE-2025-11226: QOS.CH logback-core Arbitrary Code Execution Vulnerability 5.9 medium 1.5.19 01 Oct 2025
CVE-2026-10532: Logback Core Object Injection Vulnerability 2.9 low 1.5.35 01 Jun 2026

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-core

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

Vulert records 8 vulnerabilities for ch.qos.logback:logback-core in Maven: 0 critical, 1 high, 3 medium and 4 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-core's Vulert package health score?

Vulert scores ch.qos.logback:logback-core 78/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-core 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-core 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-core have?

8 vulnerabilities are recorded for ch.qos.logback:logback-core in the Maven ecosystem: 0 critical, 1 high, 3 medium and 4 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-core vulnerabilities disclosed?

3 vulnerabilities were recorded for ch.qos.logback:logback-core in the last 12 months, and the oldest entry in this database dates to 17 Dec 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-core 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-core for upcoming vulnerabilities?

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