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.
mvn versions:use-dep-version -Dincludes=ch.qos.logback:logback-core -DdepVersion=1.5.38 -DforceVersion=trueIs your project on an affected ch.qos.logback:logback-core?
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
Logback vulnerable to Object Injection through HardenedObjectInputStream modules
- Affected
- <1.5.34
- Fixed in
- 1.5.34
QOS.CH Sarl logback logback-core has a deserialization of untrusted data vulnerability
- Affected
- <1.5.33
- Fixed in
- 1.5.33
Logback allows an attacker to instantiate classes already present on the class path
- Affected
- <1.5.25
- Fixed in
- 1.5.25
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
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
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.
| Version | Known advisories |
|---|---|
| ch.qos.logback:logback-core 1.5.38 | None |
| ch.qos.logback:logback-core 1.5.37 | None |
| ch.qos.logback:logback-core 1.5.36 | None |
| ch.qos.logback:logback-core 1.5.35 | None |
| ch.qos.logback:logback-core 1.5.34 | None |
| ch.qos.logback:logback-core 1.5.33 | CVE-2026-10532 |
| ch.qos.logback:logback-core 1.5.32 | CVE-2026-10532, CVE-2026-9828 |
| ch.qos.logback:logback-core 1.5.31 | CVE-2026-10532, CVE-2026-9828 |
| ch.qos.logback:logback-core 1.5.30 | CVE-2026-10532, CVE-2026-9828 |
| ch.qos.logback:logback-core 1.5.29 | CVE-2026-10532, CVE-2026-9828 |
| ch.qos.logback:logback-core 1.5.28 | CVE-2026-10532, CVE-2026-9828 |
| ch.qos.logback:logback-core 1.5.27 | CVE-2026-10532, CVE-2026-9828 |
| ch.qos.logback:logback-core 1.5.26 | CVE-2026-10532, CVE-2026-9828 |
| ch.qos.logback:logback-core 1.5.25 | CVE-2026-10532, CVE-2026-9828 |
| ch.qos.logback:logback-core 1.5.24 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225 |
| ch.qos.logback:logback-core 1.5.23 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225 |
| ch.qos.logback:logback-core 1.5.22 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225 |
| ch.qos.logback:logback-core 1.5.21 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225 |
| ch.qos.logback:logback-core 1.5.20 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225 |
| ch.qos.logback:logback-core 1.5.19 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225 |
| ch.qos.logback:logback-core 1.5.18 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226 |
| ch.qos.logback:logback-core 1.5.17 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226 |
| ch.qos.logback:logback-core 1.5.16 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226 |
| ch.qos.logback:logback-core 1.5.15 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226 |
| ch.qos.logback:logback-core 1.5.14 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226 |
| ch.qos.logback:logback-core 1.5.13 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226 |
| ch.qos.logback:logback-core 1.5.12 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.5.11 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.5.10 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.5.9 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.5.8 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.5.7 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.5.6 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.5.5 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.5.4 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.5.3 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.5.2 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.5.1 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.5.0 | CVE-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
- ch.qos.logback:logback-core 1.6
- ch.qos.logback:logback-core 1.4
- ch.qos.logback:logback-core 1.3
- ch.qos.logback:logback-core 1.2
- ch.qos.logback:logback-core 1.1
- ch.qos.logback:logback-core 0.9
- ch.qos.logback:logback-core 0.8
- ch.qos.logback:logback-core 0.7
- ch.qos.logback:logback-core 0.6
- ch.qos.logback:logback-core 0.5
- ch.qos.logback:logback-core 0.3
- All ch.qos.logback:logback-core 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.