Vulnerability record

CVE-2021-44832

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 9, 2026.

What it is

Reported

Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2. Source description excerpt; complete tracked detail loads below.

NVD published: Dec 29, 2021 · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026

What is affected

Reported

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

NVD published: Dec 29, 2021 · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026

Urgency and basis

Reported

Act now · 555.9

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

Exploitation evidence

Reported

kev-listed · VulnCheck KEV

VulnCheck KEV added: Feb 14, 2023 · Source record updated: Aug 9, 2026 · Tracker snapshot: Aug 9, 2026

What to do

Reported

Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Source remediation ↗

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

Evidence detail

Loading the full tracker evidence record…