Linux
apache-log4j2 security updates
Patch Radar has 16 security fixes for apache-log4j2, closing 5 CVEs, 2 of which are being exploited. The newest security fix is DLA-4444-1 (2.17.1-1~deb11u2), released January 19, 2026.
2 exploited CVEs
Latest version
n/a
Release date not known
Security fixes
16
On record in Patch Radar
CVEs
5
Closed by those fixes
Exploited
2
Vendor report or CISA KEV
Security fixes, newest first
| Priority | Fix | Release | Fixed in | CVEs | Exploited | Released |
|---|---|---|---|---|---|---|
| Routine | DLA-4444-1 | Debian 11.6 (bullseye) | 2.17.1-1~deb11u2 | 1 | Jan 19, 2026 | |
| Routine | DEBIAN-CVE-2021-44832 | Debian 12.15 (bookworm) | 2.17.1-1 | 1 | Dec 28, 2021 | |
| Routine | DEBIAN-CVE-2021-44832 | Debian 13.5 (trixie) | 2.17.1-1 | 1 | Dec 28, 2021 | |
| Routine | DEBIAN-CVE-2021-44832 | Debian 14 | 2.17.1-1 | 1 | Dec 28, 2021 | |
| Routine | DEBIAN-CVE-2021-45105 | Debian 12.15 (bookworm) | 2.17.0-1 | 1 | Dec 18, 2021 | |
| Routine | DEBIAN-CVE-2021-45105 | Debian 13.5 (trixie) | 2.17.0-1 | 1 | Dec 18, 2021 | |
| Routine | DEBIAN-CVE-2021-45105 | Debian 14 | 2.17.0-1 | 1 | Dec 18, 2021 | |
| Routine | DSA-5024-1 | Debian 11.6 (bullseye) | 2.17.0-1~deb11u1 | 1 | Dec 18, 2021 | |
| Patch now | DSA-5022-1 | Debian 11.6 (bullseye) | 2.16.0-1~deb11u1 | 1 | 1 | Dec 16, 2021 |
| Patch now | DEBIAN-CVE-2021-45046 | Debian 12.15 (bookworm) | 2.16.0-1 | 1 | 1 | Dec 14, 2021 |
| Patch now | DEBIAN-CVE-2021-45046 | Debian 13.5 (trixie) | 2.16.0-1 | 1 | 1 | Dec 14, 2021 |
| Patch now | DEBIAN-CVE-2021-45046 | Debian 14 | 2.16.0-1 | 1 | 1 | Dec 14, 2021 |
| Patch now | DSA-5020-1 | Debian 11.6 (bullseye) | 2.15.0-1~deb11u1 | 1 | 1 | Dec 11, 2021 |
| Patch now | DEBIAN-CVE-2021-44228 | Debian 12.15 (bookworm) | 2.15.0-1 | 1 | 1 | Dec 10, 2021 |
| Patch now | DEBIAN-CVE-2021-44228 | Debian 13.5 (trixie) | 2.15.0-1 | 1 | 1 | Dec 10, 2021 |
| Patch now | DEBIAN-CVE-2021-44228 | Debian 14 | 2.15.0-1 | 1 | 1 | Dec 10, 2021 |
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.