QOS.CH logback-core is vulnerable to Arbitrary Code Execution through file processing

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.9 · CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:P/VC:H/VI:L/VA:L/SC:H/SI:L/SA:L · score source

EPSS

• CVE-2025-11226: 0.19% estimated exploitation activity in the next 30 days; percentile 9.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

1 Oct 2025, 09:30 UTC

Last modified by the source

31 Oct 2025, 20:17 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-25qh-j22f-pwp8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-11226

Advisory: QOS.CH logback-core is vulnerable to Arbitrary Code Execution through file processing
IDs: CVE-2025-11226, GHSA-25qh-j22f-pwp8
Record: https://patchnext.com/advisories/cve-2025-11226 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ch.qos.logback:logback-core 1.5.19, 1.3.16. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven ch.qos.logback:logback-core: affected >= 1.4.0, < 1.5.19; < 1.3.16; fixed in 1.5.19, 1.3.16

## Suggested inspection (read-only)
- Maven ch.qos.logback:logback-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ch.qos.logback:logback-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-25qh-j22f-pwp8 (GitHub-reviewed advisory GHSA-25qh-j22f-pwp8 lists affected ranges: Maven ch.qos.logback:logback-core >=1.4.0 =0 <1.3.16)

Commands are suggestions: review each one before running it.