Logback Core
Approved changes feed: RSS · Atom
cpe:2.3:a:qos.ch_sarl:logback-core:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Qos.Ch Sarl (6a2bfb37-4deb-5f24-a0ca-d1847b749283) |
|---|---|
| Product | Logback Core (977078b8-c193-514e-b679-f66423deafe2) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-13006 |
vulnerable | 2026-07-29 00:23:32.742872 |
Incomplete protection against CVE-2025-11226
ACE vulnerability in conditional configuration file processing by QOS.CH logback-core up to and including version 1.5.36 in Java applications, allows an attacker to execute arbitrary code circumventing existing protections against CVE-2025-11226 by compromising an existing logback configuration file or by injecting an environment variable before program execution.
A successful attack requires the presence of Janino library to be present on the user's class path. In addition, the attacker must have write access to a
configuration file. Alternatively, the attacker could inject a malicious
environment variable pointing to a malicious configuration file. In both
cases, the attack requires existing privilege.
Please note that in logack version 1.5.37 conditional processing using Janino was removed.
Published: 2026-06-24T05:41:32.197Z
Updated: 2026-07-01T11:05:37.718Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-1225 |
vulnerable | 2026-06-08 07:47:14.484784 |
Malicious logback.xml configuration file allows instantiation of arbitrary classes
ACE vulnerability in configuration file processing by QOS.CH logback-core up to and including version 1.5.24 in Java applications, allows an attacker to instantiate classes already present on the class path by compromising an existing logback configuration file.
The instantiation of a potentially malicious Java class requires that said class is present on the user's class-path. In addition, the attacker must have write access to a
configuration file. However, after successful instantiation, the instance is very likely to be discarded with no further ado.
Published: 2026-01-22T09:24:14.634Z
Updated: 2026-01-22T14:14:17.842Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-11226 |
vulnerable | 2026-06-08 07:02:28.286603 |
Conditional processing of logback.xml configuration file, in conjuction with Spring Framework and Janino
ACE vulnerability in conditional configuration file processing by QOS.CH logback-core up to and including version 1.5.18 in Java applications, allows an attacker to execute arbitrary code by compromising an existing logback configuration file or by injecting an environment variable before program execution.
A successful attack requires the presence of Janino library and Spring Framework to be present on the user's class path. In addition, the attacker must have write access to a
configuration file. Alternatively, the attacker could inject a malicious
environment variable pointing to a malicious configuration file. In both
cases, the attack requires existing privilege.
Published: 2025-10-01T07:26:12.567Z
Updated: 2026-06-25T16:04:42.152Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-12798 |
vulnerable | 2026-06-08 06:25:36.122106 |
JaninoEventEvaluator vulnerability
ACE vulnerability in JaninoEventEvaluator by QOS.CH logback-core
upto including version 0.1 to 1.3.14 and 1.4.0 to 1.5.12 in Java applications allows
attacker to execute arbitrary code by compromising an existing
logback configuration file or by injecting an environment variable
before program execution.
Malicious logback configuration files can allow the attacker to execute
arbitrary code using the JaninoEventEvaluator extension.
A successful attack requires the user to have write access to a
configuration file. Alternatively, the attacker could inject a malicious
environment variable pointing to a malicious configuration file. In both
cases, the attack requires existing privilege.
Published: 2024-12-19T15:14:21.598Z
Updated: 2025-01-03T13:38:58.152Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.