[From nobody Thu Oct 15 23:43:12 2026
Received: (at submit) by bugs.debian.org; 14 Apr 2026 20:44:44 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-11.0 required=4.0 tests=BAYES_00,FROMDEVELOPER,
 MD5_SHA1_SUM,NO_RELAYS,XMAILER_REPORTBUG autolearn=ham
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 29; hammy, 150; neutral, 82; spammy,
 0. spammytokens: hammytokens:0.000-+--H*F:U*carnil,
 0.000-+--XDebbugsCc, 0.000-+--X-Debbugs-Cc, 0.000-+--HTo:N*Debian,
 0.000-+--H*Ad:N*Bug
Return-path: <carnil@debian.org>
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from <carnil@debian.org>) id 1wCkcl-006QLa-0W
 for submit@bugs.debian.org; Tue, 14 Apr 2026 20:44:43 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Salvatore Bonaccorso <carnil@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: apache-log4j2: CVE-2026-34479
Message-ID: <177619948215.262835.16939916412054781991.reportbug@eldamar.lan>
X-Mailer: reportbug 13.2.0
Date: Tue, 14 Apr 2026 22:44:42 +0200
Delivered-To: submit@bugs.debian.org

Source: apache-log4j2
Version: 2.19.0-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>

Hi,

The following vulnerability was published for apache-log4j2.

CVE-2026-34479[0]:
| The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails
| to escape characters forbidden by the XML 1.0 standard, producing
| malformed XML output. Conforming XML parsers are required to reject
| documents containing such characters with a fatal error, which may
| cause downstream log processing systems to drop or fail to index
| affected records.  Two groups of users are affected:    *  Those
| using Log4j1XmlLayout directly in a Log4j Core 2 configuration file.
| *  Those using the Log4j 1 configuration compatibility layer with
| org.apache.log4j.xml.XMLLayout specified as the layout class.
| Users are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge
| version 2.25.4, which corrects this issue.  Note: The Apache Log4j
| 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j
| 3. Users are encouraged to consult the  Log4j 1 to Log4j 2 migration
| guide https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html
| , and specifically the section on eliminating reliance on the
| bridge.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-34479
    https://www.cve.org/CVERecord?id=CVE-2026-34479
[1] https://lists.apache.org/thread/gd0hp6mj17rn3kj279vgy4p7kd4zz5on
[2] https://logging.apache.org/security.html#CVE-2026-34479
[3] https://github.com/apache/logging-log4j2/pull/4078
[4] https://github.com/apache/logging-log4j2/commit/25043cfad1bac2e43ebc4638450cbb73c51451c4

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]