Is ch.qos.logback:logback-classic 0.6 vulnerable?
Maven · 1 release from 0.6.0 to 0.6.0 · latest ch.qos.logback:logback-classic is 1.6.7 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. ch.qos.logback:logback-classic 0.6.0, the last 0.6 release, is affected by 2 known security advisories (1 critical, 1 high), including CVE-2017-5929, CVE-2023-6378. Upgrade to 1.2.13 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=ch.qos.logback:logback-classic -DdepVersion=1.2.13 -DforceVersion=trueIs your project on an affected ch.qos.logback:logback-classic?
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-classic 0.6.0
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
QOS.ch Logback vulnerable to Deserialization of Untrusted Data
- Affected
- <1.2.0
- Fixed in
- 1.2.0
Which of your client projects are still on ch.qos.logback:logback-classic 0.6?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact ch.qos.logback:logback-classic version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other ch.qos.logback:logback-classic versions
- ch.qos.logback:logback-classic 0.9
- ch.qos.logback:logback-classic 0.8
- ch.qos.logback:logback-classic 0.7
- ch.qos.logback:logback-classic 0.5
- ch.qos.logback:logback-classic 0.3
- ch.qos.logback:logback-classic 0.2
- ch.qos.logback:logback-classic 1.6
- ch.qos.logback:logback-classic 1.5
- ch.qos.logback:logback-classic 1.4
- ch.qos.logback:logback-classic 1.3
- ch.qos.logback:logback-classic 1.2
- ch.qos.logback:logback-classic 1.1
- All ch.qos.logback:logback-classic advisories
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.