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.
CVE-2021-44832
“▲” 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.
Also known asEUVD-2022-0516 (ENISA EUVD) · GHSA-8489-44mv-ggj8 (GitHub Security Advisories)Source: ENISA EUVD
- High exploitation likelihood — EPSS 98%
- Public exploit or proof-of-concept code is available
A fix is available — apply it.
- CVSS v3
- 6.6
- EG Score
- 9.0CRITICALhigh confidence
- EG Risk
- 69EG 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-12). 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, 2026Vulnerabilities in Apache Log4j Library Affecting Cisco Products: December 2021
https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-apache-log4j-qRuKNEbd[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/[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/[SECURITY] [DLA 2870-1] apache-log4j2 security update
https://lists.debian.org/debian-lts-announce/2021/12/msg00036.html[LOG4J2-3293] JDBC Appender should use JNDI Manager and JNDI access should be limited. - ASF Jira
https://issues.apache.org/jira/browse/LOG4J2-3293oss-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/1Vendor 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.
- RHSA-2022:1299Red Hat Product SecurityLow
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.4 security update
- RHSA-2022:1297Red Hat Product SecurityLow
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.4 security update
- RHSA-2022:1296Red Hat Product SecurityLow
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.4 security update
- RHSA-2022:0467Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat AMQ Streams 1.6.7 release and security update
- RHSA-2022:0223Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Integration Camel-K 1.6.3 release and security update
- RHSA-2022:0222Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat Integration Camel Extensions for Quarkus 2.2 security update
- RHSA-2022:0216Red Hat Product SecurityLow
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4 security update
- RHSA-2022:0083Red Hat Product SecurityMedium
Red Hat Security Advisory: Red Hat build of Eclipse Vert.x 4.1.8 security update
- +3 more
Patch Availability(22)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | liblog4j2-java-doc (2.17.1-0.20.04.1) @ focal | 2026-11-12 | ubuntu |
| redhat | eap7-log4j-0:2.17.1-1.redhat_00001.1.el7eap | 2022-04-11 | redhat |
| redhat | eap7-log4j-0:2.17.1-1.redhat_00001.1.el8eap | 2022-04-11 | redhat |
| redhat | org.apache.logging.log4j/log4j-api:2.17.1.redhat-00001 | 2022-04-11 | redhat |
| redhat | openshift4/ose-metering-presto:v4.7.0-202201271626.p0.g2155d34.assembly.stream | 2022-02-16 | redhat |
| redhat | openshift4/ose-metering-presto:v4.8.0-202201271626.p0.gf1abc62.assembly.stream | 2022-02-16 | redhat |
| redhat | patch | 2022-02-08 | redhat |
| redhat | openshift4/ose-logging-elasticsearch6:v4.6.0-202201181437.p0.g181b827.assembly.stream | 2022-01-27 | redhat |
| redhat | openshift3/ose-logging-elasticsearch5:v3.11.570-2.ge84e80c | 2022-01-25 | redhat |
| redhat | openshift-logging/elasticsearch6-rhel8:v6.8.1-100 | 2022-01-21 | redhat |
| redhat | patch | 2022-01-20 | redhat |
| redhat | log4j-core | 2022-01-20 | redhat |
| redhat | openshift-logging/elasticsearch6-rhel8:v6.8.1-99 | 2022-01-20 | redhat |
| redhat | openshift-logging/elasticsearch6-rhel8:v5.0.12-1 | 2022-01-20 | redhat |
| redhat | openshift-logging/elasticsearch6-rhel8:v6.8.1-98 | 2022-01-20 | redhat |
| maven | org.apache.logging.log4j:log4j-core @ 2.3.2 (fixes >= 2.0-beta7, < 2.3.2) | — | ghsa |
| maven | org.apache.logging.log4j:log4j-core @ 2.12.4 (fixes >= 2.4, < 2.12.4) | — | ghsa |
| maven | org.apache.logging.log4j:log4j-core @ 2.17.1 (fixes >= 2.13.0, < 2.17.1) | — | ghsa |
| maven | org.ops4j.pax.logging:pax-logging-log4j2 @ 1.9.2 (fixes >= 1.8.0, < 1.9.2) | — | ghsa |
| maven | org.ops4j.pax.logging:pax-logging-log4j2 @ 1.10.9 (fixes >= 1.10.0, < 1.10.9) | — | ghsa |
| maven | org.ops4j.pax.logging:pax-logging-log4j2 @ 1.11.13 (fixes >= 1.11.0, < 1.11.13) | — | ghsa |
| maven | org.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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| org.apache.logging.log4j:log4j-core | 2.13.0 ... 2.17.0 (9 versions) |
| — |
| org.ops4j.pax.logging:pax-logging-log4j2 | 2.0.0 ... 2.0.9 (14 versions) |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j2 | 2.13.3-1 ... 2.17.1-1~deb10u1 (11 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j2 | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j2 | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j2 | — |
| — |
Debian:9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j2 | 2.10.0-1 ... 2.8.2-2 (10 versions) |
| — |
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.
- Red HatRHSA-2022:0138MODERATE2021-12-28
RHSA-2022:0138 — Moderate
- Red HatRHSA-2022:0181MODERATE2021-12-28
RHSA-2022:0181 — Moderate
- Red HatRHSA-2022:0225MODERATE2021-12-28
RHSA-2022:0225 — Moderate
- Red HatRHSA-2022:0226MODERATE2021-12-28
RHSA-2022:0226 — Moderate
- Red HatRHSA-2022:0227MODERATE2021-12-28
RHSA-2022:0227 — Moderate
- Red HatRHSA-2022:0230MODERATE2021-12-28
RHSA-2022:0230 — Moderate
- Red HatRHSA-2022:0236MODERATE2021-12-28
RHSA-2022:0236 — Moderate
- Red HatRHSA-2022:0485MODERATE2021-12-28
RHSA-2022:0485 — Moderate
- Red HatRHSA-2022:0493MODERATE2021-12-28
RHSA-2022:0493 — Moderate
- UbuntuUSN-5222-1MEDIUM
Apache Log4j 2 vulnerabilities
Data Freshness Timeline
(refreshed 15× in last 7d / 52× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
Showing the most recent 100 of 158 rows on record for this CVE, as 99 entries (1 repeat merged).
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. 1 repeat row among the latest 100 is merged into the row it repeats. The 58 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-13 06:39 UTCEchelonGraph re-scored
- 2026-11-13 06:39 UTCVendor advisory
- 2026-11-13 06:39 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-12 07:33 UTCEchelonGraph re-scored
- 2026-11-12 07:33 UTCVendor advisory
- 2026-11-12 07:33 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-11 16:31 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-11-11 08:27 UTCEchelonGraph re-scored
- 2026-11-11 08:27 UTCVendor advisory
- 2026-11-11 08:27 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-10 09:21 UTCEchelonGraph re-scored
- 2026-11-10 09:21 UTCVendor advisory
- 2026-11-10 09:21 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-09 10:16 UTCEchelonGraph re-scored
- 2026-11-09 10:16 UTCVendor advisory
- 2026-11-09 10:16 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-08 11:09 UTCVendor advisory
- 2026-11-08 11:09 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-08 10:57 UTCEchelonGraph re-scored
- 2026-11-07 12:04 UTCEchelonGraph re-scored
- 2026-11-07 12:04 UTCVendor advisory
- 2026-11-07 12:04 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-06 12:57 UTCEchelonGraph re-scored
- 2026-11-06 12:57 UTCVendor advisory
- 2026-11-06 12:57 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
Show 74 moreShow fewer
- 2026-11-05 13:51 UTCEchelonGraph re-scored
- 2026-11-05 13:51 UTCVendor advisory
- 2026-11-05 13:51 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-04 16:30 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-11-04 14:45 UTCEchelonGraph re-scored
- 2026-11-04 14:45 UTCVendor advisory
- 2026-11-04 14:45 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-03 21:55 UTCOSV refresh
- 2026-11-03 16:38 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-11-03 15:39 UTCEchelonGraph re-scored
- 2026-11-03 15:39 UTCVendor advisory
- 2026-11-03 15:39 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-02 16:33 UTCVendor advisory
- 2026-11-02 16:33 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-01 21:38 UTCEchelonGraph re-scored
- 2026-11-01 21:38 UTCVendor advisory
- 2026-11-01 21:38 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-01 08:30 UTCGHSA enrichmentGHSA-8489-44mv-ggj8 · GitHub severity MODERATE · GitHub CVSS 6.6
- 2026-11-01 08:30 UTCEchelonGraph re-scored
- 2026-10-31 22:33 UTCEchelonGraph re-scored
- 2026-10-31 22:33 UTCVendor advisory
- 2026-10-30 23:27 UTCEchelonGraph re-scored
- 2026-10-30 23:27 UTCVendor advisory
- 2026-10-30 00:21 UTCEchelonGraph re-scored
- 2026-10-30 00:21 UTCVendor advisory
- 2026-10-29 01:15 UTCEchelonGraph re-scored
- 2026-10-29 01:15 UTCVendor advisory
- 2026-10-28 02:10 UTCEchelonGraph re-scored
- 2026-10-28 02:10 UTCVendor advisory
- 2026-10-27 03:02 UTCEchelonGraph re-scored
- 2026-10-27 03:02 UTCVendor advisory
- 2026-10-25 23:52 UTCVendor advisory
- 2026-10-25 18:20 UTCEchelonGraph re-scored
- 2026-10-25 16:28 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-10-25 00:47 UTCEchelonGraph re-scored
- 2026-10-25 00:47 UTCVendor advisory
- 2026-10-24 01:41 UTCEchelonGraph re-scored
- 2026-10-24 01:41 UTCVendor advisory
- 2026-10-23 16:28 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-10-23 02:35 UTCEchelonGraph re-scored
- 2026-10-23 02:35 UTCVendor advisory
- 2026-10-22 03:27 UTCEchelonGraph re-scored
- 2026-10-22 03:27 UTCVendor advisory
- 2026-10-21 04:21 UTCEchelonGraph re-scored
- 2026-10-21 04:21 UTCVendor advisory
- 2026-10-20 05:15 UTCEchelonGraph re-scored
- 2026-10-20 05:15 UTCVendor advisory
- 2026-10-19 06:08 UTCEchelonGraph re-scored
- 2026-10-19 06:08 UTCVendor advisory
- 2026-10-18 07:01 UTCEchelonGraph re-scored
- 2026-10-18 07:01 UTCVendor advisory
- 2026-10-17 07:52 UTCEchelonGraph re-scored
- 2026-10-17 07:52 UTCVendor advisory
- 2026-10-16 08:44 UTCEchelonGraph re-scored
- 2026-10-16 08:44 UTCVendor advisory
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-10-15 07:55 UTCEchelonGraph re-scored
- 2026-10-15 07:55 UTCVendor advisory
- 2026-10-14 03:53 UTCEchelonGraph re-scored
- 2026-10-14 03:53 UTCVendor advisory
- 2026-10-13 16:28 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-10-12 23:47 UTCVendor advisory
- 2026-10-12 19:07 UTCEchelonGraph re-scored
- 2026-10-11 23:33 UTCEchelonGraph re-scored
- 2026-09-30 19:14 UTCOSV refresh
- 2026-09-30 15:43 UTCEchelonGraph re-scored
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-09-19 15:38 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-09-12 01:53 UTCOSV refresh
- 2026-09-07 15:58 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 98% · 99th percentile
- 2026-09-04 05:03 UTCEPSS rescoreEPSS 98% · 99th percentile
Publicly available exploits
(2 references)Public exploit code is referenced for this CVE (1 GitHub PoC), as is 1 GitHub checker repository. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.
- GitHub checkername/log4j-scannerPublished Dec 29, 2021
Discover Log4Shell vulnerability [CVE-2021-44832]
Open source ↗ - Open source ↗GitHub PoCcckuailong/log4j_RCE_CVE-2021-44832Published Dec 29, 2021
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:9:apache-log4j2 · Maven:org.ops4j.pax.logging:pax-logging-log4j2 · Debian:11:apache-log4j2
- CVE-2021-44228EG 10.0 KEVEPSS p100CRITICAL
- CVE-2021-45105NVD 5.9EG 9.0EPSS p100CRITICAL
- CVE-2021-45046EG 9.0 KEVEPSS p100CRITICAL
- CVE-2020-9488EG 3.7EPSS p95LOW
- CVE-2017-5645EG 9.8EPSS p100CRITICAL
- CVE-2026-34480EG 7.5HIGH
- CVE-2026-34479EG 7.5HIGH
- CVE-2025-68161EG 4.8MEDIUM
- CVE-2026-34481EG 7.5HIGH
- CVE-2026-49844EG 5.9MEDIUM
Same vendor
10 shownredhat:RHSA-2022:0083 · redhat:RHSA-2022:0467 · redhat:RHSA-2022:1296
- CVE-2021-45105NVD 5.9EG 9.0EPSS p100CRITICAL
- CVE-2021-45046EG 9.0 KEVEPSS p100CRITICAL
- CVE-2022-23307NVD 8.8EG 9.8EPSS p99CRITICAL
- CVE-2022-23305EG 9.8EPSS p99CRITICAL
- CVE-2022-23302EG 8.9EPSS p99HIGH
- CVE-2021-4104NVD 7.5EG 8.9EPSS p100HIGH
- CVE-2021-27292EG 7.5HIGH
- CVE-2021-44228EG 10.0 KEVEPSS p100CRITICAL
- CVE-2021-34429NVD 5.3EG 9.0EPSS p100CRITICAL
- CVE-2021-37137EG 7.5EPSS p94HIGH
Frequently asked(5)
What is CVE-2021-44832?
When was the CVE record for CVE-2021-44832 published?
Is CVE-2021-44832 actively exploited?
What is the CVSS score of CVE-2021-44832?
How do I remediate CVE-2021-44832?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-44832
Is Your Infrastructure Affected by CVE-2021-44832?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.