Is ch.qos.logback:logback-core 1.2 vulnerable?
Maven · 14 releases from 1.2.0 to 1.2.13 · latest ch.qos.logback:logback-core is 1.6.7 · checked 18 Nov 2026
Yes: 6 known advisories
Yes. ch.qos.logback:logback-core 1.2.13, the last 1.2 release, is affected by 6 known security advisories (2 medium, 4 low), including CVE-2025-11226, CVE-2024-12798, CVE-2026-10532. 3 more affect earlier 1.2.x releases. Upgrade to 1.5.34 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=ch.qos.logback:logback-core -DdepVersion=1.5.34 -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
Advisories affecting ch.qos.logback:logback-core 1.2.13
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
Fixed within 1.2.x, affecting earlier releases
Logback is vulnerable to an attacker mounting a Denial-Of-Service attack by sending poisoned data
- Affected
- >=1.4.13 <1.4.14 · >=1.3.13 <1.3.14 · >=1.2.12 <1.2.13
- Fixed in
- 1.2.13, 1.3.14, 1.4.14
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
Deserialization of Untrusted Data in logback
- Affected
- <1.2.9
- Fixed in
- 1.2.9
Every ch.qos.logback:logback-core 1.2.x release
Affected: 1.2.0 to 1.2.13. Latest ch.qos.logback:logback-core: 1.6.7.
| Version | Known advisories |
|---|---|
| ch.qos.logback:logback-core 1.2.13 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801 |
| ch.qos.logback:logback-core 1.2.12 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6481, CVE-2023-6378 |
| ch.qos.logback:logback-core 1.2.11 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378 |
| ch.qos.logback:logback-core 1.2.10 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378 |
| ch.qos.logback:logback-core 1.2.9 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378 |
| ch.qos.logback:logback-core 1.2.8 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550 |
| ch.qos.logback:logback-core 1.2.7 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550 |
| ch.qos.logback:logback-core 1.2.6 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550 |
| ch.qos.logback:logback-core 1.2.5 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550 |
| ch.qos.logback:logback-core 1.2.4 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550 |
| ch.qos.logback:logback-core 1.2.3 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550 |
| ch.qos.logback:logback-core 1.2.2 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550 |
| ch.qos.logback:logback-core 1.2.1 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550 |
| ch.qos.logback:logback-core 1.2.0 | CVE-2026-10532, CVE-2026-9828, CVE-2026-1225, CVE-2025-11226, CVE-2024-12798, CVE-2024-12801, CVE-2023-6378, CVE-2021-42550 |
Which of your client projects are still on ch.qos.logback:logback-core 1.2?
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.5
- ch.qos.logback:logback-core 1.4
- ch.qos.logback:logback-core 1.3
- ch.qos.logback:logback-core 1.1
- ch.qos.logback:logback-core 1.0
- ch.qos.logback:logback-core 0.9
- ch.qos.logback:logback-core 1.6
- 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.