cve.bz

CVE-2026-49844 apache log4j: Improper Encoding or Escaping of Output

6.3 mediumEPSS 0.6%Fix available

Medium (6.3) in apache log4j. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.logging.log4j:log4j-api 2.25.5, 2.26.1.

On this page
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.

Severity

CVSS 4.0

6.3 medium
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

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 49th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-07-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-116 Improper Encoding or Escaping of Output
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-49844 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-49844?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-49844?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-49844 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-49844

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-49844](https://cve.bz/cve/badge/CVE-2026-49844.svg)](https://cve.bz/cve/CVE-2026-49844)

HTML:

<a href="https://cve.bz/cve/CVE-2026-49844"><img src="https://cve.bz/cve/badge/CVE-2026-49844.svg" alt="CVE-2026-49844"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Log4j APIfrom 2.13.1 before 2.25.5
Apache Software Foundation Apache Log4j APIfrom 2.26.0 before 2.26.1
Apache Software Foundation Apache Log4j APIfrom 3.0.0-alpha1 through 3.0.0-beta2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qv9r-c865-cp47Mavenorg.apache.logging.log4j:log4j-api>=2.13.1 <2.25.52.25.5
GHSA-qv9r-c865-cp47Mavenorg.apache.logging.log4j:log4j-api>=2.26.0 <2.26.12.26.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14apache-log4j2no fix listedDEBIAN-CVE-2026-49844
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 4 moreapache-log4j2no fix listedUBUNTU-CVE-2026-49844

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Important: Apache Log4j API in Red Hat products is affected by improper encoding of non-finite floating-point values during MapMessage JSON serialization. This flaw can lead to malformed JSON output when applications utilize `JsonTemplateLayout` or similar JSON serialization methods and process attacker-controlled floating-point values. The resulting invalid JSON may disrupt downstream log processing or corrupt log records, requiring specific application configurations for exploitation.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Cryostat 4log4j-apiFix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-ddb-streams-source-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-s3-sink-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-s3-source-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-sqs-sink-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-eventing-integrations-aws-sqs-source-rhel9Fix deferred
Red Hat AI Inference Serverrhaiis/vllm-cuda-rhel9Fix deferred
Red Hat AI Inference Serverrhaii/vllm-gaudi-rhel9Fix deferred
Red Hat AMQ Broker 7log4j-apiFix deferred
Red Hat AMQ Clientslog4j-apiFix deferred
Red Hat build of Apache Camel 4 for Quarkus 3log4j-apiAffected
Red Hat build of Apache Camel for Spring Boot 4log4j-apiFix deferred
Red Hat build of Apache Camel - HawtIO 4log4j-apiFix deferred
Red Hat build of Apicurio Registry 3log4j-apiUnder investigation
Red Hat Data Grid 8log4j-apiFix deferred
Red Hat Enterprise Linux 8pki-core:10.6/resteasyFix deferred
Red Hat Enterprise Linux 8pki-deps:10.6/resteasyFix deferred
Red Hat Enterprise Linux 9resteasyFix deferred
Red Hat Enterprise Linux AI (RHEL AI) 3bazel7Fix deferred
38 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-49844.

Attack patterns (CAPEC)

  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-104 Cross Zone Scripting Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON