Skip to content

[GHSA-w35j-pv5h-q9q9] Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values #7362

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ppkarwasz wants to merge 1 commit into
base: ppkarwasz/advisory-improvement-7362
Choose a base branch
from
+4 −4
Open

[GHSA-w35j-pv5h-q9q9] Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values #7362

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions advisories/github-reviewed/2026/04/GHSA-w35j-pv5h-q9q9/GHSA-w35j-pv5h-q9q9.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
{
"schema_version": "1.4.0",
"id": "GHSA-w35j-pv5h-q9q9",
"modified": "2026-04-10T21:16:54Z",
"modified": "2026-04-10T21:16:55Z",
Copy link

Copilot AI Apr 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

modified was updated, but database_specific.github_reviewed_at remains 2026-04-10T21:16:54Z, which is now earlier than the advisory's modified timestamp (2026-04-10T21:16:55Z). Since github_reviewed_at is defined as the timestamp of the last curator review, it should be updated to be >= modified (typically matching it) to avoid inconsistent metadata.

Copilot uses AI. Check for mistakes.
"published": "2026-04-10T18:31:18Z",
"aliases": [
"CVE-2026-34481"
],
"summary": "Apache Log4j's JsonTemplateLayout produces invalid JSON output when log events contain non-finite floating-point values",
"details": "Apache Log4j'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.\n\nAn attacker can exploit this issue only if both of the following conditions are met:\n\n * The application uses JsonTemplateLayout.\n * The application logs a MapMessage containing an attacker-controlled floating-point value.\n\n\nUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.",
"summary": "Apache Log4j JSON Template Layout: Improper serialization of non-finite floating-point values in JsonTemplateLayout",
"details": "Apache Log4j'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.\n\nAn attacker can exploit this issue only if both of the following conditions are met:\n\n * The application uses `JsonTemplateLayout`.\n * The application logs a `MapMessage` containing an attacker-controlled floating-point value.\n\nUsers are advised to upgrade to Apache Log4j JSON Template Layout 2.25.4, which corrects this issue.",
"severity": [
{
"type": "CVSS_V4",
Expand Down Expand Up @@ -47,7 +47,7 @@
"introduced": "3.0.0-alpha1"
},
{
"fixed": "3.0.0-beta3"
"last_affected": "3.0.0-beta3"
}
]
}
Expand Down
Loading