<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 01 Oct 2026 12:36:41 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-34481 — Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-34481</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Log4j JSON Template Layout&lt;/p&gt;
&lt;p&gt;Apache Log4j&amp;#39;s  JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.&lt;/p&gt;
&lt;p&gt;An attacker can exploit this issue only if both of the following conditions are met:&lt;/p&gt;
&lt;p&gt;*  The application uses JsonTemplateLayout.
  *  The application logs a MapMessage, or logs an object directly (e.g., via Logger.info(Object), which wraps it in an ObjectMessage), where the message contains an attacker-controlled floating-point value.&lt;/p&gt;
&lt;p&gt;Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.&lt;/p&gt;
&lt;p&gt;Note: The fix released in version 2.25.4 did not cover all affected code paths. CVE-2026-49844 was assigned to the remaining issue, which concerns the MapMessage.asJson() serialization in Apache Log4j API and is fixed in versions 2.25.5 and 2.26.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Log4j JSON Template Layout&lt;/p&gt;
&lt;p&gt;Apache Log4j&amp;#39;s  JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in versions up to and including 2.25.3, produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records.&lt;/p&gt;
&lt;p&gt;An attacker can exploit this issue only if both of the following conditions are met:&lt;/p&gt;
&lt;p&gt;*  The application uses JsonTemplateLayout.
  *  The application logs a MapMessage, or logs an object directly (e.g., via Logger.info(Object), which wraps it in an ObjectMessage), where the message contains an attacker-controlled floating-point value.&lt;/p&gt;
&lt;p&gt;Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.&lt;/p&gt;
&lt;p&gt;Note: The fix released in version 2.25.4 did not cover all affected code paths. CVE-2026-49844 was assigned to the remaining issue, which concerns the MapMessage.asJson() serialization in Apache Log4j API and is fixed in versions 2.25.5 and 2.26.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-34481</guid>
    </item>
  </channel>
</rss>
