Apache Log4j ↗

Apache · Dev / Logging

↻ RSS feed

Track your version:Monitors Apache Log4j and tailors your dashboard to that exact version.

2.26.0 · latest cycle—/100 Unknown

Summary iPlain-English security verdict for Apache Log4j, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.

Apache Log4j's security status could not be assessed at the last sync — vulnerability data was unavailable.

Disclosure trend iNew CVEs published for Apache Log4j each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.

'19

'20

'21

'22

'23

'24

'25

'26

Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.

No urgent unpatched issues identified. ✓

Get alerted about Apache Log4j

Be emailed the moment Apache Log4j gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.

We email only on real events for Apache Log4j — no marketing, no sharing, and we never know what you run. Track your whole stack →

Versions & lifecycle iWhen each release line stops receiving security patches (end-of-life). After EOL there are no more fixes — plan upgrades before these dates.

How long each Apache Log4j release line is supported — and when it sunsets. Select a line for its full report.

Dec14'21 Apache Log4j 2.12ended 2021-12-14

Oct15'15 Apache Log4j 1ended 2015-10-15

Sept20'15 Apache Log4j 2.3ended 2015-09-20

Full Apache Log4j end-of-life dates & support timeline →

2 latest 2.26.0 Supported 2.26.0 → 2.12 latest 2.12.4 End of life ended 2021-12-142.12.4 → 2.3 latest 2.3.2 End of life ended 2015-09-202.3.2 → 1 latest 1.2.17 End of life ended 2015-10-151.2.17 → See all upcoming end-of-life dates →

Frequently asked

Is Apache Log4j safe and patched?

Apache Log4j's security status could not be assessed at the last sync — vulnerability data was unavailable.

What should I do about Apache Log4j now?

Upgrade Apache Log4j to the latest supported release (2.26.0) or later and apply available security updates, then confirm against Apache's official advisory.

When does Apache Log4j reach end-of-life?

The latest supported Apache Log4j release is 2.26.0. After end-of-life a release no longer receives security patches.

Which versions of Apache Log4j are still receiving security updates?

Supported Apache Log4j release lines (latest 2.26.0): 2. End-of-life releases no longer receive security patches.

Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Apache's official advisory before you patch or upgrade — Apache Log4j official site ↗