Vulnerability record

CVE-2021-44228

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record. Tracker snapshot: Aug 8, 2026.

What it is

Reported

Apache Log4j2 contains a vulnerability where JNDI features do not protect against attacker-controlled JNDI-related endpoints, allowing for remote code execution. Source description excerpt; complete tracked detail loads below.

NVD published: Dec 10, 2021 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

What is affected

Reported

Apache — Log4j2. Product-level identification only; no affected-version conclusion is available from this field.

NVD published: Dec 10, 2021 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Urgency and basis

Reported

Act now · 574.2

Tracker decision tier from the evidence detailed below · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Exploitation evidence

Reported

Active exploitation · CISA KEV · VulnCheck KEV · ENISA exploited-vulnerability catalog

Active since: Dec 10, 2021 · CISA KEV added: Dec 10, 2021 · VulnCheck KEV added: Dec 6, 2021 · ENISA added: Dec 10, 2021 · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

What to do

Reported

For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks. Temporary mitigations using one of the measures provided at https://www.cisa.gov/uscert/ed-22-02-apache-log4j-recommended-mitigation-measures are only acceptable until updates are available.

Source remediation ↗

Tracked source remediation field · Source record updated: Aug 8, 2026 · Tracker snapshot: Aug 8, 2026

Evidence detail

Loading the full tracker evidence record…