Most recent entries from all

bdu:2026-10856

2026-10-02T13:03:46.513341+00:00

bdu:2026-10856

certfr-2026-avi-0500 — De multiples vulnérabilités ont été découvertes dans VMware Tanzu. Elles permettent à un attaquant de provoquer un prob…

2026-10-02T13:03:46.513404+00:00

certfr-2026-avi-0500

Withdrawn: CLEANSTART-2026-AA33839 — Security fixes in activemq 6.2.3-r1

2026-10-02T13:03:46.513424+00:00

Withdrawn by the publisher.

Affected: CleanStart: activemq

Package activemq version 6.2.3-r1 fixes 10 vulnerabilities: CVE-2026-34477, CVE-2026-34478, CVE-2026-34480, CVE-2026-22745, CVE-2026-22741...

EUVD-2026-290457

2026-10-02T13:03:46.513457+00:00

EUVD-2026-290457

fkie_cve-2026-34480

2026-10-02T13:03:46.513469+00:00

The impact depends on the StAX implementation in use:

* JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger.

Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.

GHSA-3pxv-7cmr-fjr4 — Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters

2026-10-02T13:03:46.513508+00:00

Affected: Maven: org.apache.logging.log4j:log4j-core

Apache Log4j Core's [`XmlLayout`](https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout), in versions up to and including 2.25.3, fails to sanitize characters forbidden by the [XML 1.0 specification](https://www.w3.org/TR/xml/#charsets), producing invalid XML output whenever a log message or MDC value contains such characters.

The impact depends on the StAX implementation in use:

* **JRE built-in StAX**: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * **Alternative StAX implementations** (e.g., [Woodstox](https://github.com/FasterXML/woodstox), a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger.

Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.

msrc_CVE-2026-34480 — Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters

2026-10-02T13:03:46.513573+00:00

msrc_CVE-2026-34480

NCSC-2026-0259 — Kwetsbaarheden verholpen in Oracle Analytics

2026-10-02T13:03:46.513590+00:00

NCSC-2026-0259

openSUSE-SU-2026:10544-1 — log4j-2.20.0-2.1 on GA media

2026-10-02T13:03:46.513610+00:00

log4j-2.20.0-2.1 on GA media

RHSA-2026:21773 — Red Hat Security Advisory: Red Hat Offline Knowledge Portal security and content update

2026-10-02T13:03:46.513627+00:00

org.eclipse.jetty/jetty-http: org.eclipse.jetty: Security bypass due to differential URI parsing org.eclipse.jetty/jetty-http: HTTP request smuggling via chunked extension quoted-string parsing org.apache.logging.log4j/log4j-core: Apache Log4j Core: Man-in-the-middle attack due to incomplete hostname verification org.apache.logging.log4j/log4j-core: Apache Log4j Core: Log injection via CRLF sequences due to configuration attribute renames org.apache.logging.log4j/log4j-1.2-api: Apache Log4j 1-to-Log4j 2 bridge: Log processing denial of service due to improper XML escaping org.apache.logging.log4j/log4j-core: Apache Log4j Core: Invalid XML output causes denial of service in logging org.apache.logging.log4j: Apache Log4j JsonTemplateLayout: Denial of Service via invalid JSON output

UBUNTU-CVE-2026-34480

2026-10-02T13:03:46.513654+00:00

Affected: Ubuntu:Pro:14.04:LTS: apache-log4j1.2, Ubuntu:Pro:16.04:LTS: apache-log4j2, Ubuntu:Pro:16.04:LTS: apache-log4j1.2, Ubuntu:18.04:LTS: apache-log4j1.2, Ubuntu:18.04:LTS: apache-log4j2, Ubuntu:20.04:LTS: apache-log4j1.2, Ubuntu:20.04:LTS: apache-log4j2, Ubuntu:22.04:LTS: apache-log4j1.2, Ubuntu:22.04:LTS: apache-log4j2, Ubuntu:24.04:LTS: apache-log4j1.2 and 5 more

Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. * Alternative StAX implementations (e.g., Woodstox https://github.com/FasterXML/woodstox , a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger. Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.

WID-SEC-W-2026-1067 — Apache log4j: Mehrere Schwachstellen ermöglichen Manipulation von Dateien

2026-10-02T13:03:46.513700+00:00

Ein Angreifer kann mehrere Schwachstellen in Apache log4j ausnutzen, um Dateien zu manipulieren.