Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Apache Log4j API versions 2.13.1 through 2.25.4 and 2.26.0 can emit invalid JSON when a MapMessage contains a NaN, Infinity, or -Infinity value, because these tokens are not permitted by RFC 8259. An attacker who can supply such a value to an application that logs MapMessage objects through JsonTemplateLayout or another JSON-producing layout can corrupt log records or disrupt downstream log parsing. Upgrade to Apache Log4j API 2.25.5 or 2.26.1.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.3 | Medium | 4.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N | CNA (apache) |
- CISA KEV Not listed.
- EPSS 0.0060, the 48th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:17 UTC First seen by agentprime
- 31 Oct 2026, 14:17 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-qv9r-c865-cp47
- OSV: GHSA-qv9r-c865-cp47
- nvd.nist.gov/vuln/detail/CVE-2026-49844
- github.com/apache/logging-log4j2/pull/4163
- github.com/apache/logging-log4j2/commit/19edb23e162d6c728a8c2221a240037d389ed300
- github.com/apache/logging-log4j2/commit/feadf8eb0b4acb6ddfa4c0ab2bbc6d88b8e12d82
- github.com/apache/logging-log4j2
- github.com/apache/logging-log4j2/releases/tag/rel/2.25.5
- github.com/apache/logging-log4j2/releases/tag/rel/2.26.1
- logging.apache.org/cyclonedx/vdr.xml
- logging.apache.org/log4j/2.x/manual/json-template-layout.html#event-template-resolver-message
- logging.apache.org/security.html#CVE-2026-49844