CVE-2026-49844

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: secondary
Trending — 4 sources updated this week
6.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.3
EG Score
6.3(low)
EPSS
51.6%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 10, 2026

Advisory Details (4)

Auto-updated Jul 10, 2026
Patch available. Sources: github_pr.
generic Patch Available

Security :: Apache Logging Services

https://logging.apache.org/security.html#CVE-2026-49844
generic

JSON Template Layout :: Apache Log4j

https://logging.apache.org/log4j/2.x/manual/json-template-layout.html#event-template-resolver-message
generic Patch Available
https://logging.apache.org/cyclonedx/vdr.xml
github_pr

Fix handling of non-finite numbers while encoding `MapMessage` to JSON

Fix merged in apache/logging-log4j2 PR #4163 on 2026-06-29 — awaiting tagged release

https://github.com/apache/logging-log4j2/pull/4163

Vendor Advisories for CVE-2026-49844(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 22:02 UTCEG score recompute
  3. 2026-07-11 22:02 UTCGHSA enrichment
  4. 2026-07-10 21:33 UTCEG score recompute
  5. 2026-07-10 21:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-49844?
CVE-2026-49844 is a medium vulnerability published on July 10, 2026. 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…
When was CVE-2026-49844 disclosed?
CVE-2026-49844 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49844 actively exploited?
CVE-2026-49844 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 51.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49844?
CVE-2026-49844 has a CVSS v3 base score of 6.3 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-49844?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49844, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49844

Explore →

Is Your Infrastructure Affected by CVE-2026-49844?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs