p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in logback

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für logback: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 5

  1. CVE-2026-13006

    Hoch · CVSS 7EPSS 0,18%Keine Korrektur veröffentlicht

    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 conf

    Veröffentlicht Aktualisiert
  2. CVE-2026-10532

    Niedrig · CVSS 2.9EPSS 0,37%Keine Korrektur veröffentlicht

    Logback deserialization whitelist bypass for Proxy objects

    Deserialization of untrusted data vulnerability in QOS.CH Sarl logback logback-core (HardenedObjectInputStream (logback-core) modules) allows Object Injection, albeit heavily restricted. More precisely, an attacker able to influence serialized data sent to SimpleSocketServer or SimpleSSLSocketServer can instantiate Proxy objects. Although deserialization is heavily restricted by HardenedObjectInputStream and no practical way to achieve remote code execution or significant privilege escalation has been identified, this issue constitutes a bypass of the intended security restrictions. This issue affects logback: through 1.5.33 inclusi

    Veröffentlicht Aktualisiert
  3. CVE-2026-9828

    Niedrig · CVSS 2.9EPSS 0,37%Keine Korrektur veröffentlicht

    Logback deserialization whitelist bypass for java.lang and java.util

    Deserialization of untrusted data vulnerability in QOS.CH Sarl logback logback-core (HardenedObjectInputStream (logback-core) modules) allows Object Injection albeit heavily restricted. More precisely, an attacker able to influence serialized data sent to SimpleSocketServer or SimpleSSLSocketServer can instantiate objects from classes in the java.lang and java.util packages that are not explicitly blocked. Although deserialization is heavily restricted by HardenedObjectInputStream and no practical way to achieve remote code execution or significant privilege escalation has been identified, this issue constitutes a bypass of the intend

    Veröffentlicht Aktualisiert
  4. CVE-2026-1225

    Niedrig · CVSS 1.8EPSS 0,16%Keine Korrektur veröffentlicht

    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.

    Veröffentlicht Aktualisiert
  5. CVE-2025-11226

    Hoch · CVSS 7EPSS 0,19%Keine Korrektur veröffentlicht

    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 a

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →