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

Maven · 39 releases from 1.5.0 to 1.5.38 · latest ch.qos.logback:logback-core is 1.6.7 · checked 18 Nov 2026

No known advisories in the last release

ch.qos.logback:logback-core 1.5.38, the last 1.5 release, has no known advisories. 6 advisories affect earlier 1.5.x releases, so update to 1.5.38.

Update within 1.5:mvn versions:use-dep-version -Dincludes=ch.qos.logback:logback-core -DdepVersion=1.5.38 -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

Fixed within 1.5.x, affecting earlier releases

  • 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

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

Affected: 1.5.0 to 1.5.33. 1.5.34 and later are not affected. Latest ch.qos.logback:logback-core: 1.6.7.

VersionKnown advisories
ch.qos.logback:logback-core 1.5.38None
ch.qos.logback:logback-core 1.5.37None
ch.qos.logback:logback-core 1.5.36None
ch.qos.logback:logback-core 1.5.35None
ch.qos.logback:logback-core 1.5.34None
ch.qos.logback:logback-core 1.5.33CVE-2026-10532
ch.qos.logback:logback-core 1.5.32CVE-2026-10532, CVE-2026-9828
ch.qos.logback:logback-core 1.5.31CVE-2026-10532, CVE-2026-9828
ch.qos.logback:logback-core 1.5.30CVE-2026-10532, CVE-2026-9828
ch.qos.logback:logback-core 1.5.29CVE-2026-10532, CVE-2026-9828
ch.qos.logback:logback-core 1.5.28CVE-2026-10532, CVE-2026-9828
ch.qos.logback:logback-core 1.5.27CVE-2026-10532, CVE-2026-9828
ch.qos.logback:logback-core 1.5.26CVE-2026-10532, CVE-2026-9828
ch.qos.logback:logback-core 1.5.25CVE-2026-10532, CVE-2026-9828
ch.qos.logback:logback-core 1.5.24CVE-2026-10532, CVE-2026-9828, CVE-2026-1225
ch.qos.logback:logback-core 1.5.23CVE-2026-10532, CVE-2026-9828, CVE-2026-1225
ch.qos.logback:logback-core 1.5.22CVE-2026-10532, CVE-2026-9828, CVE-2026-1225
ch.qos.logback:logback-core 1.5.21CVE-2026-10532, CVE-2026-9828, CVE-2026-1225
ch.qos.logback:logback-core 1.5.20CVE-2026-10532, CVE-2026-9828, CVE-2026-1225
ch.qos.logback:logback-core 1.5.19CVE-2026-10532, CVE-2026-9828, CVE-2026-1225
ch.qos.logback:logback-core 1.5.18CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226
ch.qos.logback:logback-core 1.5.17CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226
ch.qos.logback:logback-core 1.5.16CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226
ch.qos.logback:logback-core 1.5.15CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226
ch.qos.logback:logback-core 1.5.14CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226
ch.qos.logback:logback-core 1.5.13CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226
ch.qos.logback:logback-core 1.5.12CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801
ch.qos.logback:logback-core 1.5.11CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801
ch.qos.logback:logback-core 1.5.10CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801
ch.qos.logback:logback-core 1.5.9CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801
ch.qos.logback:logback-core 1.5.8CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801
ch.qos.logback:logback-core 1.5.7CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801
ch.qos.logback:logback-core 1.5.6CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801
ch.qos.logback:logback-core 1.5.5CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801
ch.qos.logback:logback-core 1.5.4CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801
ch.qos.logback:logback-core 1.5.3CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801
ch.qos.logback:logback-core 1.5.2CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801
ch.qos.logback:logback-core 1.5.1CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801
ch.qos.logback:logback-core 1.5.0CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801

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

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.