Most recent entries from all

certfr-2026-avi-0958 — De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquan…

2026-10-02T17:31:28.312651+00:00

certfr-2026-avi-0958

CLEANSTART-2026-AP60356 — Security fix for CVE-2026-49844 applied in: activemq 6.2.8-r2, activemq 6.3.1-r1, apache-hive 4.0.1-r11, apache-hive 4.…

2026-10-02T17:31:28.312721+00:00

Affected: CleanStart: activemq, CleanStart: apache-hive, CleanStart: apache-nifi-registry, CleanStart: elasticsearch, CleanStart: flink, CleanStart: kafka, CleanStart: rundeck, CleanStart: solr, CleanStart: spark-sc213-jdk17-py312, CleanStart: trino and 1 more

CVE-2026-49844 affects multiple packages. This issue is resolved in later releases. See references for individual vulnerability details.

EUVD-2026-371385

2026-10-02T17:31:28.312784+00:00

EUVD-2026-371385

fkie_cve-2026-49844

2026-10-02T17:31:28.312798+00:00

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.

GHSA-qv9r-c865-cp47 — Apache Log4j API: Improper encoding of non-finite floating-point values during MapMessage JSON serialization

2026-10-02T17:31:28.312838+00:00

Affected: Maven: org.apache.logging.log4j:log4j-api

The defect is reachable only when both of the following conditions hold:

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.

NCSC-2026-0375 — Kwetsbaarheden verholpen in Oracle Communications

2026-10-02T17:31:28.312873+00:00

NCSC-2026-0375

OESA-2026-3153 — log4j security update

2026-10-02T17:31:28.312921+00:00

Affected: openEuler:24.03-LTS-SP1: log4j, openEuler:24.03-LTS-SP3: log4j, openEuler:24.03-LTS-SP4: log4j, openEuler:20.03-LTS-SP4: log4j, openEuler:22.03-LTS-SP4: log4j

Log4j is a tool to help the programmer output log statements to a variety of output targets. Security Fix(es):

Apache Log4j's JsonTemplateLayout in versions up to and including 2.25.3 produces invalid JSON output when log events contain non-finite floating-point values (NaN, Infinity, or -Infinity), which are prohibited by RFC 8259. This may cause downstream log processing systems to reject or fail to index affected records. An attacker can exploit this issue only if both of the following conditions are met: 1) The application uses JsonTemplateLayout; 2) The application logs a MapMessage containing an attacker-controlled floating-point value.(CVE-2026-34481)

The defect is reachable only when both of the following conditions hold:

UBUNTU-CVE-2026-49844

2026-10-02T17:31:28.312967+00:00

Affected: Ubuntu:Pro:16.04:LTS: apache-log4j2, Ubuntu:18.04:LTS: apache-log4j2, Ubuntu:20.04:LTS: apache-log4j2, Ubuntu:22.04:LTS: apache-log4j2, Ubuntu:24.04:LTS: apache-log4j2, Ubuntu:26.04:LTS: apache-log4j2

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.

WID-SEC-W-2026-2292 — Apache log4j und Log4cxx: Mehrere Schwachstellen ermöglichen Manipulation von Dateien

2026-10-02T17:31:28.313003+00:00

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Apache log4j und Apache Log4cxx ausnutzen, um Dateien zu manipulieren.