Is ch.qos.logback:logback-core 0.9 vulnerable?

Maven · 31 releases from 0.9.0 to 0.9.30 · latest ch.qos.logback:logback-core is 1.6.7 · checked 18 Nov 2026

Yes: 9 known advisories

Yes. ch.qos.logback:logback-core 0.9.30, the last 0.9 release, is affected by 9 known security advisories (1 critical, 1 high, 3 medium, 4 low), including CVE-2017-5929, CVE-2023-6378, CVE-2025-11226. Upgrade to 1.5.34 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=ch.qos.logback:logback-core -DdepVersion=1.5.34 -DforceVersion=true

Is your project on an affected ch.qos.logback:logback-core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting ch.qos.logback:logback-core 0.9.30

  • LowCVE-2026-10532GHSA-jhq6-gfmj-v8fx1 Jun 2026

    Logback vulnerable to Object Injection through HardenedObjectInputStream modules

    Affected
    <1.5.34
    Fixed in
    1.5.34
  • LowCVE-2026-9828GHSA-p47f-322f-whfh28 May 2026

    QOS.CH Sarl logback logback-core has a deserialization of untrusted data vulnerability

    Affected
    <1.5.33
    Fixed in
    1.5.33
  • LowCVE-2026-1225GHSA-qqpg-mvqg-649v22 Jan 2026

    Logback allows an attacker to instantiate classes already present on the class path

    Affected
    <1.5.25
    Fixed in
    1.5.25
  • MediumCVE-2025-11226GHSA-25qh-j22f-pwp81 Oct 2025

    QOS.CH logback-core is vulnerable to Arbitrary Code Execution through file processing

    Affected
    >=1.4.0 <1.5.19 · <1.3.16
    Fixed in
    1.3.16, 1.5.19
  • MediumCVE-2024-12798GHSA-pr98-23f8-jwxv19 Dec 2024

    QOS.CH logback-core Expression Language Injection vulnerability

    Affected
    >=1.4.0 <1.5.13 · <1.3.15
    Fixed in
    1.3.15, 1.5.13
  • LowCVE-2024-12801GHSA-6v67-2wr5-gvf419 Dec 2024

    QOS.CH logback-core Server-Side Request Forgery vulnerability

    Affected
    >=1.4.0 <1.5.13 · <1.3.15
    Fixed in
    1.3.15, 1.5.13
  • HighCVE-2023-6378GHSA-vmq6-5m68-f53m29 Nov 2023

    logback serialization vulnerability

    Affected
    >=1.3.0 <1.3.12 · >=1.4.0 <1.4.12 · <1.2.13
    Fixed in
    1.2.13, 1.3.12, 1.4.12
  • MediumCVE-2021-42550GHSA-668q-qrv7-99fm17 Dec 2021

    Deserialization of Untrusted Data in logback

    Affected
    <1.2.9
    Fixed in
    1.2.9
  • CriticalCVE-2017-5929GHSA-vmfg-rjjm-rjrj7 Jun 2021

    QOS.ch Logback vulnerable to Deserialization of Untrusted Data

    Affected
    <1.2.0
    Fixed in
    1.2.0

Every ch.qos.logback:logback-core 0.9.x release

Affected: 0.9.0 to 0.9.30. Latest ch.qos.logback:logback-core: 1.6.7.

VersionKnown advisories
ch.qos.logback:logback-core 0.9.30CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.29CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.28CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.27CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.26CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.25CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.24CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.23CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.22CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.21CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.20CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.19CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.18CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.17CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.16CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.15CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.14CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.13CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.12CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.11CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.10CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.9CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.8CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.7CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.6CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.5CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.4CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.3CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.2CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.1CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929
ch.qos.logback:logback-core 0.9.0CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550, CVE-2017-5929

Which of your client projects are still on ch.qos.logback:logback-core 0.9?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact ch.qos.logback:logback-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

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