Apache Software Foundation
Apache Log4j Core
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-34480 | 10 Apr 2026 | 2.0-alpha1 < 2.25.4; 3.0.0-alpha1 ≤ 3.0.0-beta3 | Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings. The References section of this erratum contains a download link (you must log in to download the update). | Update reference ↗ |
| CVE-2026-34478 | 10 Apr 2026 | 2.21.0 < 2.25.4; 3.0.0-beta1 ≤ 3.0.0-beta3 | Before applying the update, back up your existing installation, including all applications, configuration files, databases and database settings. The References section of this erratum contains a download link (you must log in to download the update). | Update reference ↗ |
| CVE-2026-34477 | 10 Apr 2026 | 2.12.0 < 2.25.4; 3.0.0-alpha1 ≤ 3.0.0-beta3 | The container image provided by this update can be downloaded from the Red Hat container registry at registry.redhat.io using the "podman pull" command. | Update reference ↗ |
| CVE-2025-68161 | 18 Dec 2025 | 2.0-beta9 < 2.25.3; 3.0.0-alpha1 ≤ 3.0.0-beta3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.