{"api_version":"v1","generated_at":"2026-10-05T23:55:00+00:00","product":{"cve_count":2,"evidence_gap_note":"This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.","id":"security:cve-apache-log4j2-a4541e16e809","lifecycle_state":"evidence_gap","linked_lifecycle_url":null,"name":"Log4j2","next_cursor":null,"observations":[{"affected":"Apache Log4j: Apache Log4j2 < 2.16.0","affected_versions_present":true,"cve_id":"CVE-2021-45046","cve_url":"https://cve.blacktree.nl/cve/CVE-2021-45046","fixed":"Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258","last_modified":"2025-10-21T23:25:22.768Z","patch_url":"https://access.redhat.com/security/cve/CVE-2021-45046","primary_source":"","published":"2021-12-14T16:55:09.000Z"},{"affected":"Apache Log4j2: 2.0-beta9 < log4j-core*","affected_versions_present":true,"cve_id":"CVE-2021-44228","cve_url":"https://cve.blacktree.nl/cve/CVE-2021-44228","fixed":"Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258","last_modified":"2025-10-21T23:25:23.121Z","patch_url":"https://access.redhat.com/security/cve/CVE-2021-44228","primary_source":"","published":"2021-12-10T00:00:00.000Z"}],"source_generated_at":"2026-10-05T06:20:29.126Z","vendor":"Apache"}}