24h | 7d | 30d

Overview

  • Apache Software Foundation
  • Apache Log4j API
  • org.apache.logging.log4j:log4j-api

10 Jul 2026
Published
17 Sep 2026
Updated

CVSS v4.0
MEDIUM (6.3)
EPSS
0.60%

KEV

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.

Statistics

  • 1 Post

Last activity: 1 hour ago

Bluesky

Profile picture fallback
This addresses the following vulnerabilities: CVE-2026-19032 CVE-2026-49844 CVE-2026-68497 CVE-2026-83557 CVE-2026-89407 CVE-2026-89425 CVE-2026-91776 CVE-2026-91777 N/A Security fixes for apigee-hybrid-cassandra-client
  • 0
  • 0
  • 0
  • 1h ago

Overview

  • FasterXML
  • jackson-core
  • com.fasterxml.jackson.core:jackson-core

23 Sep 2026
Published
23 Sep 2026
Updated

CVSS v3.1
HIGH (7.5)
EPSS
0.62%

KEV

Description

UTF8DataInputJsonParser._reportInvalidToken() in FasterXML jackson-core builds the offending-token text for its error message by appending Java identifier characters to a StringBuilder in a loop that has no upper bound. Unlike the three sibling parser implementations, including UTF8StreamJsonParser, it never consults ErrorReportConfiguration.getMaxErrorTokenLength() (default 256). A malformed token supplied to a parser created through JsonFactory.createParser(DataInput) is therefore accumulated in full. No StreamReadConstraints setting mitigates this: maxDocumentLength cannot be applied to DataInput sources at all, and maxStringLength does not cover this path because the accumulation bypasses ReadConstrainedTextBuffer. The reporter measured a 20,000,109-character exception message from a 20-million-character malformed token on the DataInput path, against 367 characters for identical input on the InputStream path. Scaling the payload drives the StringBuilder, which also incurs byte-to-char expansion and internal array doubling, to many times the raw payload size and can trigger OutOfMemoryError for the whole JVM. UTF8DataInputJsonParser was introduced in 2.8.0 together with createParser(DataInput); releases before 2.8.0 do not contain the affected class.

Statistics

  • 1 Post

Last activity: 1 hour ago

Bluesky

Profile picture fallback
This addresses the following vulnerabilities: CVE-2026-19032 CVE-2026-49844 CVE-2026-68497 CVE-2026-83557 CVE-2026-89407 CVE-2026-89425 CVE-2026-91776 CVE-2026-91777 N/A Security fixes for apigee-hybrid-cassandra-client
  • 0
  • 0
  • 0
  • 1h ago
Showing 131 to 132 of 132 CVEs