Skip to content

← Public intelligence

Maven package

org.apache.logging.log4j:log4j-layout-template-json

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.3MavenPublished

    Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout

    CVE-2026-34481 · GHSA-w35j-pv5h-q9q9

    Affected
    • Maven org.apache.logging.log4j:log4j-layout-template-json >= 2.14.0, < 2.25.4; >= 3.0.0-alpha1, <= 3.0.0-beta3
    Fixed in
    2.25.4· Partial vendor fix
    Issue
    Apache Log4j's JsonTemplateLayout, 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. An attacker can exploit this issue only if both of the following conditions are met: The application uses JsonTemplateLayout. The application logs a MapMessage containing an attacker-controlled floating-point value. Users are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.

    Recommended action: Upgrade to 2.25.4; some affected versions have no fix yet, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →