CVE-2021-44228

CRITICALNVD 10.010.0—
EchelonGraph scoreHIGH confidence

Score elevated to 10.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-12-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 10.0 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Exploited in the wild
10.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 100%CVSS: 10.0Exploit: cisa kev · ssvc active · kev ransomware · Metasploit · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.

CVSS v3
10.0
EG Score
10.0CRITICALhigh confidence
EG Risk
100
EG Risk 100/100CISA SSVC

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
Severity100% × 45%
Exploitation100% × 40%
Automatability100% × 15%
CISA SSVC: Attend at low mission impact; Act at medium or high.
Action: A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
100%
EPSS %ILE
100th
KEV
⚠ Exploited

CISA SSVCAttend at low mission impact; Act at medium or high.

A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

December 10, 2021

Last Modified

August 11, 2026

Advisory Details (10)

Auto-updated Oct 6, 2026
Patch available.
generic

Packet Storm

http://packetstormsecurity.com/files/165371/VMware-Security-Advisory-2021-0028.4.html
generic

Packet Storm

http://packetstormsecurity.com/files/165311/log4j-scan-Extensive-Scanner.html
generic

Packet Storm

http://packetstormsecurity.com/files/165307/Log4j-Remote-Code-Execution-Word-Bypassing.html
generic

Packet Storm

http://packetstormsecurity.com/files/165306/L4sh-Log4j-Remote-Code-Execution.html
generic

Packet Storm

http://packetstormsecurity.com/files/165282/Log4j-Payload-Generator.html
generic

Packet Storm

http://packetstormsecurity.com/files/165281/Log4j2-Log4Shell-Regexes.html
generic

Packet Storm

http://packetstormsecurity.com/files/165270/Apache-Log4j2-2.14.1-Remote-Code-Execution.html
generic

Packet Storm

http://packetstormsecurity.com/files/165261/Apache-Log4j2-2.14.1-Information-Disclosure.html
generic

Packet Storm

http://packetstormsecurity.com/files/165260/VMware-Security-Advisory-2021-0028.html
generic

Packet Storm

http://packetstormsecurity.com/files/165225/Apache-Log4j2-2.14.1-Remote-Code-Execution.html

Vendor Advisories for CVE-2021-44228(20)

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

Patch Availability(20)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuliblog4j2-java-doc (2.4-2ubuntu0.1~esm1) @ xenial2026-10-10ubuntu
ubuntuliblog4j2-java (2.15.0-0.21.10.1) @ impish2026-10-10ubuntu
ubuntuliblog4j2-java (2.16.0-0.21.10.1) @ impish2026-10-10ubuntu
redhateap7-wildfly-0:7.3.12-3.GA_redhat_00002.1.el7eap2025-02-24redhat
redhateap7-wildfly-0:7.1.9-2.GA_redhat_00002.1.ep7.el72025-02-24redhat
redhatlog4j-core2022-01-26redhat
redhatpatch2022-01-11redhat
redhatopenshift4/ose-metering-presto:v4.6.0-202112150545.p0.g190688a.assembly.art35952021-12-16redhat
redhatopenshift4/ose-metering-hive:v4.6.0-202112140546.p0.g8b9da97.assembly.stream2021-12-16redhat
redhatopenshift4/ose-metering-presto:v4.7.0-202112150631.p0.gd502108.assembly.4.7.402021-12-16redhat
redhatorg.apache.logging.log4j/log4j-api:2.17.1.redhat-000022021-12-15redhat
redhatopenshift4/ose-metering-presto:v4.8.0-202112150431.p0.g4b934ae.assembly.art35992021-12-15redhat
redhatopenshift3/ose-logging-elasticsearch5:v3.11.570-2.gd1198202021-12-14redhat
redhatpatch2021-12-14redhat
redhatopenshift4/ose-metering-hive:v4.8.0-202112132154.p0.g57dd03a.assembly.stream2021-12-14redhat
redhatpatch2021-12-14redhat
redhatopenshift-logging/elasticsearch6-rhel8:v6.8.1-672021-12-14redhat
redhatopenshift-logging/elasticsearch6-rhel8:v6.8.1-652021-12-14redhat
redhatopenshift-logging/elasticsearch6-rhel8:v6.8.1-662021-12-14redhat
redhatopenshift-logging/elasticsearch6-rhel8:v5.0.10-12021-12-14redhat

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

(11 across 7 ecosystems)
Maven(5)
PackageVulnerable rangeFix by version rangeDependents
com.guicedee.services:log4j-core1.0.10.0 ... 1.2.1.2-jre17 (362 versions)
  • every version through 1.2.1.2-jre17: no fix on record
—
org.apache.logging.log4j:log4j-core2.10.0 ... 2.9.1 (18 versions)
  • 2.13.0 up to 2.15.0: fixed in 2.15.0
  • 2.0-beta9 up to 2.3.1: fixed in 2.3.1
  • 2.4 up to 2.12.2: fixed in 2.12.2
—
org.ops4j.pax.logging:pax-logging-log4j22.0.0 ... 2.0.9 (11 versions)
  • 1.8.0 up to 1.9.2: fixed in 1.9.2
  • 1.10.0 up to 1.10.8: fixed in 1.10.8
  • 1.11.0 up to 1.11.10: fixed in 1.11.10
  • 2.0.0 up to 2.0.11: fixed in 2.0.11
—
org.xbib.elasticsearch:log4j6.3.2.1——
uk.co.nichesolutions.logging.log4j:log4j-core2.6.3-CUSTOM——
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j22.11.1-2, 2.11.2-1, 2.13.3-1
  • every version up to 2.15.0-1~deb10u1: fixed in 2.15.0-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j22.13.3-1, 2.15.0-1~deb10u1
  • every version up to 2.15.0-1~deb11u1: fixed in 2.15.0-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j2—
  • every version up to 2.15.0-1: fixed in 2.15.0-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j2—
  • every version up to 2.15.0-1: fixed in 2.15.0-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j2—
  • every version up to 2.15.0-1: fixed in 2.15.0-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j22.7-2
  • every version up to 2.7-2+deb9u1: fixed in 2.7-2+deb9u1
—

Weakness Classification(4)

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

Additional Vendor Advisories

(6)

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 41× in last 7d / 187× 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.

Showing the most recent 100 of 821 total refreshes for this CVE.

  1. 2026-10-10 18:02 UTCVendor advisory
  2. 2026-10-10 13:53 UTCVendor advisory
  3. 2026-10-10 09:42 UTCVendor advisory
  4. 2026-10-10 05:32 UTCVendor advisory
  5. 2026-10-10 01:20 UTCVendor advisory
  6. 2026-10-09 21:11 UTCVendor advisory
  7. 2026-10-09 17:00 UTCVendor advisory
  8. 2026-10-09 12:49 UTCVendor advisory
  9. 2026-10-09 08:41 UTCVendor advisory
  10. 2026-10-09 04:29 UTCVendor advisory
  11. 2026-10-09 00:20 UTCVendor advisory
  12. 2026-10-08 20:12 UTCVendor advisory
  13. 2026-10-08 16:03 UTCVendor advisory
  14. 2026-10-08 11:53 UTCVendor advisory
  15. 2026-10-08 07:44 UTCVendor advisory
  16. 2026-10-08 03:35 UTCVendor advisory
  17. 2026-10-07 23:26 UTCVendor advisory
  18. 2026-10-07 19:17 UTCVendor advisory
  19. 2026-10-07 15:08 UTCVendor advisory
  20. 2026-10-07 10:59 UTCVendor advisory
  21. 2026-10-07 06:50 UTCVendor advisory
  22. 2026-10-07 02:41 UTCVendor advisory
  23. 2026-10-06 22:32 UTCVendor advisory
  24. 2026-10-06 18:23 UTCVendor advisory
  25. 2026-10-06 14:14 UTCVendor advisory
Show 75 more
  1. 2026-10-06 10:05 UTCVendor advisory
  2. 2026-10-06 05:53 UTCVendor advisory
  3. 2026-10-06 01:45 UTCVendor advisory
  4. 2026-10-05 21:36 UTCVendor advisory
  5. 2026-10-05 17:26 UTCVendor advisory
  6. 2026-10-05 13:18 UTCVendor advisory
  7. 2026-10-05 09:09 UTCVendor advisory
  8. 2026-10-05 04:59 UTCVendor advisory
  9. 2026-10-05 00:49 UTCVendor advisory
  10. 2026-10-04 20:37 UTCVendor advisory
  11. 2026-10-04 16:28 UTCVendor advisory
  12. 2026-10-04 12:19 UTCVendor advisory
  13. 2026-10-04 08:10 UTCVendor advisory
  14. 2026-10-04 04:00 UTCVendor advisory
  15. 2026-10-03 23:52 UTCVendor advisory
  16. 2026-10-03 19:43 UTCVendor advisory
  17. 2026-10-03 15:34 UTCVendor advisory
  18. 2026-10-03 11:25 UTCVendor advisory
  19. 2026-10-03 07:15 UTCVendor advisory
  20. 2026-10-03 03:06 UTCVendor advisory
  21. 2026-10-02 22:57 UTCVendor advisory
  22. 2026-10-02 18:46 UTCVendor advisory
  23. 2026-10-02 14:38 UTCVendor advisory
  24. 2026-10-02 10:28 UTCVendor advisory
  25. 2026-10-02 06:19 UTCVendor advisory
  26. 2026-10-02 02:11 UTCVendor advisory
  27. 2026-10-01 22:01 UTCVendor advisory
  28. 2026-10-01 17:51 UTCVendor advisory
  29. 2026-10-01 13:42 UTCVendor advisory
  30. 2026-10-01 09:34 UTCVendor advisory
  31. 2026-10-01 05:24 UTCVendor advisory
  32. 2026-10-01 01:15 UTCVendor advisory
  33. 2026-09-30 21:05 UTCVendor advisory
  34. 2026-09-30 16:56 UTCVendor advisory
  35. 2026-09-30 12:48 UTCVendor advisory
  36. 2026-09-30 08:39 UTCVendor advisory
  37. 2026-09-30 04:30 UTCVendor advisory
  38. 2026-09-30 00:19 UTCVendor advisory
  39. 2026-09-29 20:10 UTCVendor advisory
  40. 2026-09-29 15:59 UTCVendor advisory
  41. 2026-09-29 11:50 UTCVendor advisory
  42. 2026-09-29 07:41 UTCVendor advisory
  43. 2026-09-29 03:33 UTCVendor advisory
  44. 2026-09-28 23:22 UTCEG score recompute
  45. 2026-09-28 23:22 UTCVendor advisory
  46. 2026-09-28 19:13 UTCVendor advisory
  47. 2026-09-28 15:03 UTCVendor advisory
  48. 2026-09-28 10:51 UTCVendor advisory
  49. 2026-09-28 06:42 UTCVendor advisory
  50. 2026-09-28 02:32 UTCVendor advisory
  51. 2026-09-27 22:23 UTCVendor advisory
  52. 2026-09-27 21:51 UTCCISA KEV update
  53. 2026-09-27 18:14 UTCVendor advisory
  54. 2026-09-27 14:05 UTCVendor advisory
  55. 2026-09-27 09:56 UTCVendor advisory
  56. 2026-09-27 05:48 UTCVendor advisory
  57. 2026-09-27 01:39 UTCVendor advisory
  58. 2026-09-26 21:28 UTCVendor advisory
  59. 2026-09-26 17:19 UTCVendor advisory
  60. 2026-09-26 13:11 UTCVendor advisory
  61. 2026-09-26 09:00 UTCVendor advisory
  62. 2026-09-26 04:48 UTCVendor advisory
  63. 2026-09-26 00:39 UTCVendor advisory
  64. 2026-09-25 20:28 UTCVendor advisory
  65. 2026-09-25 19:35 UTCCISA KEV update
  66. 2026-09-25 16:19 UTCVendor advisory
  67. 2026-09-25 14:55 UTCCISA KEV update
  68. 2026-09-25 12:11 UTCVendor advisory
  69. 2026-09-25 08:02 UTCVendor advisory
  70. 2026-09-25 03:53 UTCVendor advisory
  71. 2026-09-24 23:44 UTCVendor advisory
  72. 2026-09-24 19:35 UTCVendor advisory
  73. 2026-09-24 19:31 UTCCISA KEV update
  74. 2026-09-24 15:26 UTCVendor advisory
  75. 2026-09-24 11:17 UTCVendor advisory

Publicly available exploits

(10 references)

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

  • Metasploitexploit/multi/http/log4shell_header_injection✓ verified
    First seen Dec 14, 2021

    Rapid7-maintained Metasploit module exploiting Log4j JNDI lookup injection via HTTP headers.

    Open source ↗
  • Metasploitexploit/linux/http/mobileiron_core_log4shell✓ verified
    First seen Dec 12, 2021

    MobileIron Core Unauthenticated JNDI Injection RCE (via Log4Shell)

    Open source ↗
  • GitHub PoCkozmer/log4j-shell-poc✓ verified
    First seen Dec 11, 2021

    Self-contained Python PoC with a built-in LDAP+HTTP listener — minimal setup.

    Open source ↗
  • Metasploitauxiliary/scanner/http/log4shell_scanner✓ verified
    First seen Dec 9, 2021

    Log4Shell HTTP Scanner

    Open source ↗
  • Metasploitexploit/multi/http/log4shell_header_injection✓ verified
    First seen Dec 9, 2021

    Log4Shell HTTP Header Injection

    Open source ↗
  • Metasploitexploit/multi/http/ubiquiti_unifi_log4shell✓ verified
    First seen Dec 9, 2021

    UniFi Network Application Unauthenticated JNDI Injection RCE (via Log4Shell)

    Open source ↗
  • Metasploitexploit/multi/http/vmware_vcenter_log4shell✓ verified
    First seen Dec 9, 2021

    VMware vCenter Server Unauthenticated JNDI Injection RCE (via Log4Shell)

    Open source ↗
  • Exploit-DBEDB-51183
    First seen Apr 1, 2023

    AD Manager Plus 7122 - Remote Code Execution (RCE)

    Open source ↗
  • Exploit-DBEDB-50590
    First seen Dec 14, 2021

    Apache Log4j2 2.14.1 - Information Disclosure

    Open source ↗
  • Exploit-DBEDB-50592
    First seen Dec 14, 2021

    Apache Log4j 2 - Remote Code Execution (RCE)

    Open source ↗

Past incidents using this CVE

(1)

This CVE was central to one or more publicly-documented breaches. Each card links to authoritative reporting at the time of the incident.

  • Log4Shell (Apache Log4j)Dec 2021

    JNDI lookup injection in Log4j, a ubiquitous Java logging library. Pre-auth unauthenticated RCE; Apache Foundation called it the worst vulnerability in a decade. Active exploitation continues 3+ years later.

    Source: Wired

Related CVEs(same product + same vendor + same CWE)

Frequently asked(6)

What is CVE-2021-44228?
CVE-2021-44228 is a critical vulnerability published on December 10, 2021. Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message…
When was CVE-2021-44228 disclosed?
CVE-2021-44228 was first published on December 10, 2021, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-44228 actively exploited?
Yes. CISA added CVE-2021-44228 to the Known Exploited Vulnerabilities catalog on December 10, 2021, affecting Apache Log4j2. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2021-44228?
CVE-2021-44228 has a CVSS v3 base score of 10.0 (NVD).
Which products are affected by CVE-2021-44228?
CVE-2021-44228 affects Apache Log4j2. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2021-44228?
A fix for CVE-2021-44228 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-44228 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2021-44228?

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

Book a Demo →Browse All CVEs