Get real-time updates on Telegram
CVE-2026-34481: log4j from 2.14.0 (inclusive), before 2.25.4 (exclusive), 3.0.0 · update alpha1, 3.0.0 · update alpha1_rc1 (+4 more…
CVE-2026-34481. CVSS 3.1 base score 7.5 (HIGH, NVD). EPSS 0.00691 (percentile 0.52551), scored 26-Oct-2026.
Affected technology
log4j · from 2.14.0 (inclusive), before 2.25.4 (exclusive)
apache
log4j · 3.0.0 · update alpha1
apache
log4j · 3.0.0 · update alpha1_rc1
apache
log4j · 3.0.0 · update alpha1_rc2
apache
log4j · 3.0.0 · update beta1
apache
log4j · 3.0.0 · update beta2
apache
log4j · 3.0.0 · update beta3
apache
Apache Log4j JSON Template Layout · 2.14.0 to before 2.25.4, 3.0.0-alpha1 through 3.0.0-beta3
Apache Software Foundation
Component: Not specified by the source
Attack conditions (Vendor/CNA, CVSS 4.0): Network (remote) · No privileges required · No user interaction required
What an attacker can do
An attacker can exploit this issue only if both of the following conditions are met: * The application uses JsonTemplateLayout. * The application logs a MapMessage, or logs an object directly (e.g., via Logger.info(Object), which wraps it in an ObjectMessage), where the message contains an attacker-controlled floating-point value. Vendor/CNA’s CVSS 4.0 assessment (base score 6.3/10) rates confidentiality, integrity and availability impact as none.
- CWE
- CWE-116
- CCR priority
- 30.2 /100 (P4)
- CVSS 3.1
- 7.5 /10 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N · NVD
- EPSS
- 0.00718 · percentile 0.54405 · 2026-11-15
- KEV
- no
Provenance
- FIRST EPSS daily exploit-probability · Source record · observed 2026-11-16 06:41:02.068004+00:00 UTC
- NVD CVE API 2.0 · Source record · observed 2026-10-27 00:51:15.792435+00:00 UTC
- OSV.dev · Source record · observed 2026-10-27 11:47:01.753480+00:00 UTC
Stable permalink: https://cybercodered.org/item/cve-cve-2026-34481.html