Summary
QOS.CH logback-core is vulnerable to Arbitrary Code Execution through file processing
QOS.CH logback-core versions up to 1.5.18 contain an ACE vulnerability in conditional configuration file processing in Java applications. This vulnerability allows an attacker to execute arbitrary code by compromising an existing logback configuration file or by injecting a malicious environment variable before program execution.
A successful attack requires the Janino library and Spring Framework to be present on the user's class path. Additionally, 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 privileges.
Impact
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
ch.qos.logback:logback-core to 1.5.19 or later; ch.qos.logback:logback-core to 1.3.16 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-11226? CVE-2025-11226 is a medium-severity improper input validation vulnerability in ch.qos.logback:logback-core (maven), affecting versions >= 1.4.0, < 1.5.19. It is fixed in 1.5.19, 1.3.16. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
- Which versions of ch.qos.logback:logback-core are affected by CVE-2025-11226? ch.qos.logback:logback-core (maven) versions >= 1.4.0, < 1.5.19 is affected.
- Is there a fix for CVE-2025-11226? Yes. CVE-2025-11226 is fixed in 1.5.19, 1.3.16. Upgrade to this version or later.
- Is CVE-2025-11226 exploitable, and should I be worried? Whether CVE-2025-11226 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-11226 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-11226?
- Upgrade
ch.qos.logback:logback-coreto 1.5.19 or later - Upgrade
ch.qos.logback:logback-coreto 1.3.16 or later
- Upgrade