[From nobody Thu Oct 15 23:43:12 2026
Received: (at submit) by bugs.debian.org; 12 Jul 2026 20:23:00 +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=-10.9 required=4.0 tests=BAYES_00,FOURLA,
 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, 22; hammy, 150; neutral, 121; spammy,
 0. spammytokens: hammytokens:0.000-+--H*F:U*carnil,
 0.000-+--XDebbugsCc, 0.000-+--X-Debbugs-Cc, 0.000-+--H*Ad:N*Bug,
 0.000-+--H*Ad:N*Tracking
Return-path: <carnil@debian.org>
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from <carnil@debian.org>) id 1wj0hW-003rKM-35
 for submit@bugs.debian.org; Sun, 12 Jul 2026 20:23:00 +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-49844
Message-ID: <178388777670.27040.334105470170457160.reportbug@eldamar.lan>
X-Mailer: reportbug 13.2.0+nmu1
Date: Sun, 12 Jul 2026 22:22:56 +0200
Delivered-To: submit@bugs.debian.org

Source: apache-log4j2
Version: 2.19.0-2
Severity: important
Tags: security upstream
Forwarded: https://github.com/apache/logging-log4j2/pull/4163
X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>

Hi,

The following vulnerability was published for apache-log4j2.

CVE-2026-49844[0]:
| Improper encoding of non-finite floating-point values during
| MapMessage JSON serialization in Apache Log4j API produces output
| that is not valid JSON. This issue affects Apache Log4j API versions
| 2.13.1 through 2.25.4 and version 2.26.0.  The fix for
| CVE-2026-34481 did not cover all code paths: when a MapMessage
| contains a non-finite IEEE 754 value (NaN, Infinity, or -Infinity),
| MapMessage.asJson() emits the corresponding bare token. RFC 8259
| does not permit these tokens, so a conformant parser rejects the
| resulting document.  The defect is reachable only when both of the
| following conditions hold:    *  The application uses the  message
| resolver https://logging.apache.org/log4j/2.x/manual/json-template-
| layout.html#event-template-resolver-message  of JsonTemplateLayout
| or any other layout that relies on MapMessage.asJson() or
| MapMessage.getFormattedMessage(new String[]{"JSON"}).   *  The
| application logs a MapMessage that contains an attacker-controlled
| floating-point value.   An attacker who can supply a non-finite
| value can cause the affected layout to emit malformed JSON, which
| may corrupt the enclosing log record or disrupt downstream log
| ingestion and parsing.  Users are advised to upgrade to Apache Log4j
| API 2.25.5 or 2.26.1, both of which emit RFC 8259-compliant JSON for
| non-finite values.


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-49844
    https://www.cve.org/CVERecord?id=CVE-2026-49844
[1] https://logging.apache.org/security.html#CVE-2026-49844
[2] https://github.com/apache/logging-log4j2/pull/4163
[3] https://github.com/apache/logging-log4j2/commit/19edb23e162d6c728a8c2221a240037d389ed300

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]