CVE-2021-44832

CRITICALNVD 6.69.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 98% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 6.6 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2022-0516 (ENISA EUVD) · GHSA-8489-44mv-ggj8 (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 98%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 98%CVSS: 6.6Exploit: Public PoCExposed services: Not assessed

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.0CRITICALhigh confidence
EG Risk
69
EG Risk 69/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity66% × 45%
Impact severity (EG Severity): CVSS 6.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation98% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
98%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 6.6 MEDIUM): a likelihood of exploitation, not impact.

EG Severity
6.6 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
98% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

December 28, 2021

Last Modified

June 17, 2026

Advisory Details (9)

Auto-updated Sep 20, 2026
Patch available.
Web page

Vulnerabilities in Apache Log4j Library Affecting Cisco Products: December 2021

https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd
Web page

[SECURITY] Fedora 34 Update: log4j-2.17.1-1.fc34 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/T57MPJUW3MA6QGWZRTMCHHMMPQNVKGFC/
Web page

[SECURITY] Fedora 35 Update: log4j-2.17.1-1.fc35 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EVV25FXL4FU5X6X5BSL7RLQ7T6F65MRA/
Web pageMentions a patch (unverified)

[SECURITY] [DLA 2870-1] apache-log4j2 security update

https://lists.debian.org/debian-lts-announce/2021/12/msg00036.html
Web page

[LOG4J2-3293] JDBC Appender should use JNDI Manager and JNDI access should be limited. - ASF Jira

https://issues.apache.org/jira/browse/LOG4J2-3293
Web page

oss-security - CVE-2021-44832: Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration

http://www.openwall.com/lists/oss-security/2021/12/28/1

Patch Availability(22)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuliblog4j2-java (2.17.1-0.21.04.1) @ hirsute2026-11-01ubuntu
redhateap7-log4j-0:2.17.1-1.redhat_00001.1.el7eap2022-04-11redhat
redhateap7-log4j-0:2.17.1-1.redhat_00001.1.el8eap2022-04-11redhat
redhatorg.apache.logging.log4j/log4j-api:2.17.1.redhat-000012022-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
redhatlog4j-core2022-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
mavenorg.apache.logging.log4j:log4j-core @ 2.3.2 (fixes >= 2.0-beta7, < 2.3.2)—ghsa
mavenorg.apache.logging.log4j:log4j-core @ 2.12.4 (fixes >= 2.4, < 2.12.4)—ghsa
mavenorg.apache.logging.log4j:log4j-core @ 2.17.1 (fixes >= 2.13.0, < 2.17.1)—ghsa
mavenorg.ops4j.pax.logging:pax-logging-log4j2 @ 1.9.2 (fixes >= 1.8.0, < 1.9.2)—ghsa
mavenorg.ops4j.pax.logging:pax-logging-log4j2 @ 1.10.9 (fixes >= 1.10.0, < 1.10.9)—ghsa
mavenorg.ops4j.pax.logging:pax-logging-log4j2 @ 1.11.13 (fixes >= 1.11.0, < 1.11.13)—ghsa
mavenorg.ops4j.pax.logging:pax-logging-log4j2 @ 2.0.14 (fixes >= 2.0.0, < 2.0.14)—ghsa

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

(7 across 6 ecosystems)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
org.apache.logging.log4j:log4j-core2.13.0 ... 2.17.0 (9 versions)
  • 2.0-beta7 up to 2.3.2: fixed in 2.3.2
  • 2.4 up to 2.12.4: fixed in 2.12.4
  • 2.13.0 up to 2.17.1: fixed in 2.17.1
—
org.ops4j.pax.logging:pax-logging-log4j22.0.0 ... 2.0.9 (14 versions)
  • 1.8.0 up to 1.9.2: fixed in 1.9.2
  • 1.10.0 up to 1.10.9: fixed in 1.10.9
  • 1.11.0 up to 1.11.13: fixed in 1.11.13
  • 2.0.0 up to 2.0.14: fixed in 2.0.14
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j22.13.3-1 ... 2.17.1-1~deb10u1 (11 versions)
  • every version up to 2.17.1-1~deb11u1: fixed in 2.17.1-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j2—
  • every version up to 2.17.1-1: fixed in 2.17.1-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j2—
  • every version up to 2.17.1-1: fixed in 2.17.1-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j2—
  • every version up to 2.17.1-1: fixed in 2.17.1-1
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j22.10.0-1 ... 2.8.2-2 (10 versions)
  • every version up to 2.12.4-0+deb9u1: fixed in 2.12.4-0+deb9u1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 17× in last 7d / 50× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 90 of 109 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 10 repeat rows among the latest 100 are merged into the row they repeat. The 19 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 21:38 UTCEG score recompute
  2. 2026-11-01 21:38 UTCVendor advisory
  3. 2026-11-01 21:38 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
  4. 2026-11-01 08:30 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
  5. 2026-11-01 08:30 UTCEG score recompute
  6. 2026-10-31 22:33 UTCEG score recompute
  7. 2026-10-31 22:33 UTCVendor advisory
  8. 2026-10-30 23:27 UTCEG score recompute
  9. 2026-10-30 23:27 UTCVendor advisory
  10. 2026-10-30 00:21 UTCEG score recompute
  11. 2026-10-30 00:21 UTCVendor advisory
  12. 2026-10-29 01:15 UTCEG score recompute
  13. 2026-10-29 01:15 UTCVendor advisory
  14. 2026-10-28 02:10 UTCEG score recompute
  15. 2026-10-28 02:10 UTCVendor advisory
  16. 2026-10-27 03:02 UTCEG score recompute
  17. 2026-10-27 03:02 UTCVendor advisory
  18. 2026-10-25 23:52 UTCVendor advisory
  19. 2026-10-25 18:20 UTCEG score recompute
  20. 2026-10-25 16:28 UTCEPSS rescoreEPSS 98% · 99th percentile
  21. 2026-10-25 00:47 UTCEG score recompute
  22. 2026-10-25 00:47 UTCVendor advisory
  23. 2026-10-24 01:41 UTCEG score recompute
  24. 2026-10-24 01:41 UTCVendor advisory
  25. 2026-10-23 16:28 UTCEPSS rescoreEPSS 98% · 99th percentile
Show 65 more
  1. 2026-10-23 02:35 UTCEG score recompute
  2. 2026-10-23 02:35 UTCVendor advisory
  3. 2026-10-22 03:27 UTCEG score recompute
  4. 2026-10-22 03:27 UTCVendor advisory
  5. 2026-10-21 04:21 UTCEG score recompute
  6. 2026-10-21 04:21 UTCVendor advisory
  7. 2026-10-20 05:15 UTCEG score recompute
  8. 2026-10-20 05:15 UTCVendor advisory
  9. 2026-10-19 06:08 UTCEG score recompute
  10. 2026-10-19 06:08 UTCVendor advisory
  11. 2026-10-18 07:01 UTCEG score recompute
  12. 2026-10-18 07:01 UTCVendor advisory
  13. 2026-10-17 07:52 UTCEG score recompute
  14. 2026-10-17 07:52 UTCVendor advisory
  15. 2026-10-16 08:44 UTCEG score recompute
  16. 2026-10-16 08:44 UTCVendor advisory
  17. 2026-10-15 16:28 UTCEPSS rescoreEPSS 98% · 99th percentile
  18. 2026-10-15 07:55 UTCEG score recompute
  19. 2026-10-15 07:55 UTCVendor advisory
  20. 2026-10-14 03:53 UTCEG score recompute
  21. 2026-10-14 03:53 UTCVendor advisory
  22. 2026-10-13 16:28 UTCEPSS rescoreEPSS 98% · 99th percentile
  23. 2026-10-12 23:47 UTCVendor advisory
  24. 2026-10-12 19:07 UTCEG score recompute
  25. 2026-10-11 23:33 UTCEG score recompute
  26. 2026-09-30 19:14 UTCOSV refresh
  27. 2026-09-30 15:43 UTCEG score recompute
  28. 2026-09-30 15:00 UTCEPSS rescoreEPSS 98% · 99th percentile
  29. 2026-09-24 14:00 UTCEPSS rescoreEPSS 98% · 99th percentile
  30. 2026-09-19 15:38 UTCEPSS rescoreEPSS 98% · 99th percentile
  31. 2026-09-12 01:53 UTCOSV refresh
  32. 2026-09-07 15:58 UTCEPSS rescoreEPSS 98% · 99th percentile
  33. 2026-09-06 13:45 UTCEPSS rescoreEPSS 98% · 99th percentile
  34. 2026-09-04 13:57 UTCEPSS rescoreEPSS 98% · 99th percentile
  35. 2026-09-04 05:03 UTCEPSS rescoreEPSS 98% · 99th percentile
  36. 2026-09-01 13:50 UTCEPSS rescoreEPSS 98% · 99th percentile
  37. 2026-08-30 19:14 UTCEPSS rescoreEPSS 98% · 99th percentile
  38. 2026-08-28 21:37 UTCEPSS rescoreEPSS 98% · 99th percentile
  39. 2026-08-24 14:13 UTCEPSS rescoreEPSS 98% · 99th percentile
  40. 2026-08-24 07:28 UTCOSV refresh
  41. 2026-08-19 17:01 UTCEPSS rescoreEPSS 98% · 99th percentile
  42. 2026-08-18 13:45 UTCEPSS rescoreEPSS 98% · 99th percentile
  43. 2026-08-17 13:44 UTCEPSS rescoreEPSS 98% · 99th percentile
  44. 2026-08-16 14:53 UTCEPSS rescoreEPSS 98% · 99th percentile
  45. 2026-08-16 02:11 UTCEPSS rescoreEPSS 98% · 99th percentile
  46. 2026-08-12 13:48 UTCEPSS rescoreEPSS 98% · 99th percentile
  47. 2026-08-08 04:19 UTCOSV refresh
  48. 2026-07-23 02:05 UTCEG score recompute
  49. 2026-07-22 21:21 UTCEG score recompute▲ 2.40
  50. 2026-07-22 21:21 UTCVendor advisory
  51. 2026-07-21 15:22 UTCEPSS rescoreEPSS 98% · 99th percentile
  52. 2026-07-12 21:37 UTCOSV refresh
  53. 2026-07-09 19:07 UTCEPSS rescoreEPSS 98% · 99th percentile
  54. 2026-06-30 23:20 UTCEPSS rescoreEPSS 98% · 99th percentile
  55. 2026-06-24 07:20 UTCOSV refresh
  56. 2026-06-23 21:31 UTCEPSS rescoreEPSS 98% · 99th percentile
  57. 2026-06-15 17:46 UTCEPSS rescoreEPSS 98% · 99th percentile
  58. 2026-06-14 23:15 UTCEPSS rescoreEPSS 54% · 98th percentile
  59. 2026-06-12 23:10 UTCEPSS rescoreEPSS 54% · 98th percentile
  60. 2026-06-11 13:58 UTCEPSS rescoreEPSS 54% · 98th percentile
  61. 2026-06-10 22:16 UTCEPSS rescoreEPSS 54% · 98th percentile
  62. 2026-06-08 14:15 UTCEPSS rescoreEPSS 54% · 98th percentile
  63. 2026-06-07 10:59 UTCOSV refresh
  64. 2026-06-06 13:46 UTCEPSS rescoreEPSS 54% · 98th percentile
  65. 2026-06-05 22:45 UTCEPSS rescoreEPSS 54% · 98th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

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

Frequently asked(5)

What is CVE-2021-44832?
CVE-2021-44832 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2021-44832 published?
The CVE record for CVE-2021-44832 was published on December 28, 2021. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
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 (99th percentile of EPSS-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 + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2021-44832?
A fix for CVE-2021-44832 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2021-44832 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-44832

Explore →

Is Your Infrastructure Affected by CVE-2021-44832?

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