CVE-2026-13006 json
Incomplete protection against CVE-2025-11226
published 2026-06-24 4 mo ago modified 2026-10-25 14 d ago also EUVD-2026-38691
- cvss
- 7.0
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- QOS.CH Sarl Logback-core 1.5.37
- logback Debian 14 1:1.6.3-1
debian advisories DEBIAN-CVE-2026-13006
- logback openSUSE Tumbleweed 1.5.36-1.1
opensuse advisories openSUSE-SU-2026:11135-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-13006 updated cvss 6.0
logback-core: Logback-core: Arbitrary Code Execution via Malicious Configuration or Environment Variable
-
Red Hat Migration Toolkit for Applications 8 mta/mta-cli-rhel9, mta/mta-java-external-provider-rhel9 Red Hat OpenShift Serverless openshift-serverless-1/kn-ekb-receiver-rhel9, openshift-serverless-1/kn-ekb-dispatcher-rhel9 Red Hat AMQ Broker 7 logback-core Red Hat AMQ Clients logback-core Red Hat build of Apache Camel - HawtIO 4 logback-core Red Hat build of Apache Camel for Spring Boot 4 logback-coreaffected: no fix available “Fix deferred”
+15 more productsfewer
Red Hat build of Debezium 3 logback-core Red Hat Data Grid 8 logback-core Red Hat Enterprise Linux 8 log4j, slf4j, log4j-jcl, log4j-web, slf4j-ext, slf4j-jcl, +10 more Red Hat Enterprise Linux 9 slf4j, slf4j-jcl, slf4j-jdk14, jul-to-slf4j, slf4j-manual, slf4j-javadoc, +4 more Red Hat Enterprise Linux 10 slf4j Red Hat Fuse 7 logback-core Red Hat JBoss Enterprise Application Platform 7 logback-core Red Hat JBoss Enterprise Application Platform 8 logback-core Red Hat JBoss Enterprise Application Platform Expansion Pack logback-core Red Hat JBoss Web Server 6 logback-core Red Hat OpenShift Dev Spaces devspaces/server-rhel9, devspaces/openvsx-rhel9, devspaces/pluginregistry-rhel9 Red Hat Satellite 6 candlepin, puppetserver, openvox-server, candlepin-selinux Red Hat Single Sign-On 7 logback-core Red Hat streams for Apache Kafka 2 logback-core Red Hat streams for Apache Kafka 3 logback-core
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 4 mo ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 7.0 | CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N/S:P/AU:N/RE:M/U:Green |
| CNA | 4.0 | 7.0 | CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:N/R:X/V:X/RE:M/U:Green |
Affected products
- QOS.CH Sarl Logback-core
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
Sources
- CVE List CVE-2026-13006
- NVD CVE-2026-13006
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.