CVE-2021-44832

CRITICALNVD 6.69.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 98% probability of exploitation within the next 30 days (top 0.1% of all CVEs). NVD baseline CVSS 6.6 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 98%
CISA-KEV: Not listedEPSS PROB: 98%CVSS: 6.6Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.6
EG Score
9.0(high)
EG Risk
80(Track)
EG Risk 80/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation98% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
98%
EPSS %ILE
100%
KEV
Not listed

Published

December 28, 2021

Last Modified

June 17, 2026

References (24)

Vendor Advisories for CVE-2021-44832(11)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuliblog4j2-java-doc (2.17.1-0.20.04.1) @ focal2026-05-23ubuntu
redhateap7-log4j-0:2.17.1-1.redhat_00001.1.el8eap2022-04-11redhat
redhateap7-log4j-0:2.17.1-1.redhat_00001.1.el7eap2022-04-11redhat
redhatlog4j-core2022-04-11redhat
redhatopenshift4/ose-metering-presto:v4.7.0-202201271626.p0.g2155d34.assembly.stream2022-02-16redhat
redhatopenshift4/ose-metering-presto:v4.8.0-202201271626.p0.gf1abc62.assembly.stream2022-02-16redhat
redhatpatch2022-02-08redhat
redhatopenshift4/ose-logging-elasticsearch6:v4.6.0-202201181437.p0.g181b827.assembly.stream2022-01-27redhat
redhatopenshift3/ose-logging-elasticsearch5:v3.11.570-2.ge84e80c2022-01-25redhat
redhatopenshift-logging/elasticsearch6-rhel8:v6.8.1-1002022-01-21redhat
redhatpatch2022-01-20redhat
redhatopenshift-logging/elasticsearch6-rhel8:v6.8.1-992022-01-20redhat
redhatopenshift-logging/elasticsearch6-rhel8:v5.0.12-12022-01-20redhat
redhatopenshift-logging/elasticsearch6-rhel8:v6.8.1-982022-01-20redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
org.apache.logging.log4j:log4j-core2.13.0 ... 2.17.0 (9 versions)2.17.1—
org.ops4j.pax.logging:pax-logging-log4j22.0.0 ... 2.0.9 (14 versions)2.0.14—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 5× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:05 UTCEG score recompute
  2. 2026-07-22 21:21 UTCEG score recompute▲ 2.40
  3. 2026-07-22 21:21 UTCVendor advisory
  4. 2026-07-21 15:22 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-12 21:37 UTCOSV refresh
  7. 2026-07-09 19:07 UTCEPSS rescore
  8. 2026-06-30 23:20 UTCEPSS rescore
  9. 2026-06-30 23:20 UTCEPSS rescore
  10. 2026-06-24 07:20 UTCOSV refresh
  11. 2026-06-23 21:31 UTCEPSS rescore
  12. 2026-06-23 21:31 UTCEPSS rescore
  13. 2026-06-15 17:46 UTCEPSS rescore
  14. 2026-06-14 23:15 UTCEPSS rescore
  15. 2026-06-14 23:15 UTCEPSS rescore
  16. 2026-06-12 23:10 UTCEPSS rescore
  17. 2026-06-11 13:58 UTCEPSS rescore
  18. 2026-06-11 13:58 UTCEPSS rescore
  19. 2026-06-10 22:16 UTCEPSS rescore
  20. 2026-06-10 22:16 UTCEPSS rescore
  21. 2026-06-08 14:15 UTCEPSS rescore
  22. 2026-06-08 14:15 UTCEPSS rescore
  23. 2026-06-07 10:59 UTCOSV refresh
  24. 2026-06-06 13:46 UTCEPSS rescore
  25. 2026-06-06 13:46 UTCEPSS rescore
Show 20 more
  1. 2026-06-05 22:45 UTCEPSS rescore
  2. 2026-06-05 06:09 UTCEPSS rescore
  3. 2026-06-05 06:09 UTCEPSS rescore
  4. 2026-06-04 13:10 UTCEPSS rescore
  5. 2026-06-04 13:10 UTCEPSS rescore
  6. 2026-06-02 20:11 UTCEPSS rescore
  7. 2026-06-02 20:11 UTCEPSS rescore
  8. 2026-05-31 22:29 UTCEPSS rescore
  9. 2026-05-31 22:29 UTCEPSS rescore
  10. 2026-05-31 00:15 UTCEPSS rescore
  11. 2026-05-31 00:15 UTCEPSS rescore
  12. 2026-05-29 13:42 UTCEPSS rescore
  13. 2026-05-28 13:43 UTCEPSS rescore
  14. 2026-05-28 13:43 UTCEPSS rescore
  15. 2026-05-27 13:39 UTCEPSS rescore
  16. 2026-05-27 13:39 UTCEPSS rescore
  17. 2026-05-26 13:42 UTCEPSS rescore
  18. 2026-05-26 13:42 UTCEPSS rescore
  19. 2026-05-23 04:00 UTCEG score recompute
  20. 2026-05-23 04:00 UTCVendor advisory

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCcckuailong/log4j_RCE_CVE-2021-44832
    First seen Dec 29, 2021
    Open source ↗

Frequently asked(5)

What is CVE-2021-44832?
CVE-2021-44832 is a critical vulnerability published on December 28, 2021. 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…
When was CVE-2021-44832 disclosed?
CVE-2021-44832 was first published in the National Vulnerability Database on December 28, 2021, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-44832 actively exploited?
CVE-2021-44832 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98% probability of exploitation in the next 30 days, which ranks it in the top 0.1% of all scored CVEs.
What is the CVSS score of CVE-2021-44832?
CVE-2021-44832 has a CVSS v3 base score of 6.6 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2021-44832?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-44832, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-44832

Explore →

Is Your Infrastructure Affected by CVE-2021-44832?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs