JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
CVE-2021-4104
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 8.9 because EPSS predicted 81% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.
Also known asEUVD-2021-2514 (ENISA EUVD) · GHSA-fp5r-v3w9-4333 (GitHub Security Advisories)Source: ENISA EUVD
- High exploitation likelihood — EPSS 81%
- Public exploit or proof-of-concept code is available
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 8.9HIGHhigh confidence
- EG Risk
- 66EG Risk 66/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)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation81% × 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 every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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
- 81%
- 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 (8.9): severity, escalated by confirmed exploitation. This CVE's 8.9 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 81% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 14, 2021
Last Modified
May 28, 2026
Advisory Details (10)
Auto-updated May 29, 2026Arduino: Remote Code Execution (GLSA 202312-04) — Gentoo security
https://security.gentoo.org/glsa/202312-04Minecraft Server: Remote Code Execution (GLSA 202312-02) — Gentoo security
https://security.gentoo.org/glsa/202312-02Ubiquiti UniFi: remote code execution via bundled log4j (GLSA 202310-16) — Gentoo security
https://security.gentoo.org/glsa/202310-16IBM Spectrum Protect: Multiple Vulnerabilities (GLSA 202209-02) — Gentoo security
https://security.gentoo.org/glsa/202209-02Restrict LDAP access via JNDI
Patch available: apache/logging-log4j2 rel/2.21.0 (PR #608 merged 2021-12-05)
https://github.com/apache/logging-log4j2/pull/608#issuecomment-990494126oss-security - CVE-2022-23302: Deserialization of untrusted data in JMSSink in Apache Log4j 1.x
http://www.openwall.com/lists/oss-security/2022/01/18/3Vendor Advisories for CVE-2021-4104(20)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2024:10207Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.3.11 Security update
- RHSA-2024:5856Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.1.7 on RHEL 7 security update
- RHSA-2022:5460Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 6.4.24 security update
- RHSA-2022:5459Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 6.4.24 security update
- RHSA-2022:5458Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 6.4.24 security update
- 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
- +12 more
Patch Availability(24)
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 |
|---|---|---|---|
| log4j:log4j | 1.2.11 ... 1.2.9 (13 versions) |
| — |
| org.zenframework.z8.dependencies.commons:log4j-1.2.17 | 2.0 |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j1.2 | 1.2.17-10 |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j1.2 | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j1.2 | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j1.2 | — |
| — |
Debian:9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j1.2 | 1.2.17-7, 1.2.17-7+deb9u1 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(19)
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-2021:5107MODERATE2021-12-10
RHSA-2021:5107 — Moderate
- Red HatRHSA-2021:5141MODERATE2021-12-10
RHSA-2021:5141 — Moderate
- Red HatRHSA-2021:5148MODERATE2021-12-10
RHSA-2021:5148 — Moderate
- Red HatRHSA-2021:5183MODERATE2021-12-10
RHSA-2021:5183 — Moderate
- Red HatRHSA-2021:5184MODERATE2021-12-10
RHSA-2021:5184 — Moderate
- Red HatRHSA-2021:5186MODERATE2021-12-10
RHSA-2021:5186 — Moderate
- Red HatRHSA-2021:5206MODERATE2021-12-10
RHSA-2021:5206 — Moderate
- Red HatRHSA-2021:5269MODERATE2021-12-10
RHSA-2021:5269 — Moderate
- Red HatRHSA-2022:0289MODERATE2021-12-10
RHSA-2022:0289 — Moderate
- Red HatRHSA-2022:0290MODERATE2021-12-10
RHSA-2022:0290 — Moderate
- Red HatRHSA-2022:0291MODERATE2021-12-10
RHSA-2022:0291 — Moderate
- Red HatRHSA-2022:0294MODERATE2021-12-10
RHSA-2022:0294 — Moderate
- Red HatRHSA-2022:0430MODERATE2021-12-10
RHSA-2022:0430 — Moderate
- Red HatRHSA-2022:0435MODERATE2021-12-10
RHSA-2022:0435 — Moderate
- Red HatRHSA-2022:0436MODERATE2021-12-10
RHSA-2022:0436 — Moderate
- Red HatRHSA-2022:0437MODERATE2021-12-10
RHSA-2022:0437 — Moderate
- Red HatRHSA-2022:0438MODERATE2021-12-10
RHSA-2022:0438 — Moderate
- Red HatRHSA-2022:0444MODERATE2021-12-10
RHSA-2022:0444 — Moderate
- Red HatRHSA-2022:0446MODERATE2021-12-10
RHSA-2022:0446 — Moderate
Data Freshness Timeline
(refreshed 6× in last 7d / 25× 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 87 of 104 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. 13 repeat rows among the latest 100 are merged into the row they repeat. The 17 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-10-30 16:30 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-29 16:29 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-28 15:32 UTCEG score recompute
- 2026-10-28 15:32 UTCVendor advisory
- 2026-10-28 15:32 UTCGHSA enrichmentGHSA-fp5r-v3w9-4333 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-27 16:28 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-25 18:22 UTCEG score recompute
- 2026-10-25 16:29 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-24 16:29 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-22 16:29 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-21 16:28 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-21 09:00 UTCEG score recompute
- 2026-10-21 09:00 UTCVendor advisory
- 2026-10-21 09:00 UTCGHSA enrichmentGHSA-fp5r-v3w9-4333 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-18 08:54 UTCEG score recompute
- 2026-10-17 16:29 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-17 13:25 UTCOSV refresh
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-12 19:10 UTCEG score recompute
- 2026-10-11 23:35 UTCEG score recompute
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 81% · 99th percentile
Show 62 moreShow fewer
- 2026-10-02 16:23 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-30 15:41 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-26 15:54 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-25 10:06 UTCOSV refresh
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-23 13:45 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-22 14:44 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-21 20:28 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-18 19:24 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-17 19:23 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-06 01:30 UTCOSV refresh
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-09-01 13:51 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-30 19:14 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-30 01:19 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-28 21:38 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-26 14:43 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-25 13:46 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-24 14:13 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-21 23:46 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-19 17:01 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-19 12:59 UTCOSV refresh
- 2026-08-17 13:44 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-16 02:11 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-13 21:57 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-12 13:48 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-08-04 08:27 UTCOSV refresh
- 2026-07-28 15:33 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-26 14:52 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-24 14:15 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-23 14:16 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-23 02:04 UTCEG score recompute▲ 1.40
- 2026-07-22 22:50 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-21 15:22 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-20 17:05 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-18 05:59 UTCOSV refresh
- 2026-07-16 17:00 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-15 16:55 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-13 22:27 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-09 19:07 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-07 13:43 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-04 06:29 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-07-01 15:04 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-06-30 23:20 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-06-30 02:30 UTCOSV refresh
- 2026-06-28 14:05 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-06-27 03:06 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-06-25 13:48 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-06-23 21:31 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-06-21 01:58 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-06-16 17:51 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-06-15 17:46 UTCEPSS rescoreEPSS 81% · 99th percentile
- 2026-06-14 23:15 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-06-13 22:58 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-06-12 23:10 UTCEPSS rescoreEPSS 72% · 98th percentile
- 2026-06-12 15:10 UTCOSV refresh
- 2026-06-11 13:58 UTCEPSS rescoreEPSS 72% · 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/log4shell_1.xPublished Dec 14, 2021
log4j 1.x RCE Poc -- CVE-2021-4104
Open source ↗
Related CVEs(same product + same vendor + same CWE)
Same product
6 shownDebian:9:apache-log4j1.2 · Debian:11:apache-log4j1.2 · Maven:log4j:log4j
Same vendor
10 shownredhat:RHSA-2022:0289 · redhat:RHSA-2021:5107 · redhat:RHSA-2022:1296
- CVE-2022-23307NVD 8.8EG 9.8EPSS p99CRITICAL
- CVE-2022-23305EG 9.8EPSS p99CRITICAL
- CVE-2022-23302EG 8.9EPSS p99HIGH
- CVE-2021-45046EG 9.0 KEVEPSS p100CRITICAL
- CVE-2021-44228EG 10.0 KEVEPSS p100CRITICAL
- CVE-2021-44832NVD 6.6EG 9.0EPSS p100CRITICAL
- CVE-2021-45105NVD 5.9EG 9.0EPSS p100CRITICAL
- CVE-2020-13935NVD 7.5EG 9.0EPSS p100CRITICAL
- CVE-2021-4125EG 8.1HIGH
- CVE-2021-3859EG 7.5HIGH
Same CWE
10 shownCWE-502
- CVE-2021-45046EG 9.0 KEVEPSS p100CRITICAL
- CVE-2021-42550EG 6.6EPSS p92MEDIUM
- CVE-2021-44228EG 10.0 KEVEPSS p100CRITICAL
- CVE-2021-42130EG 8.9EPSS p99HIGH
- CVE-2021-42127EG 9.8EPSS p99CRITICAL
- CVE-2021-42125NVD 8.8EG 9.0EPSS p100CRITICAL
- CVE-2021-36336EG 9.8CRITICAL
- CVE-2021-44682EG 9.8CRITICAL
- CVE-2021-44681EG 9.8CRITICAL
- CVE-2021-44680EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2021-4104?
When was the CVE record for CVE-2021-4104 published?
Is CVE-2021-4104 actively exploited?
What is the CVSS score of CVE-2021-4104?
How do I remediate CVE-2021-4104?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-4104
Is Your Infrastructure Affected by CVE-2021-4104?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.