CVE-2021-44228 · Log4Shell
No source can show you its own past. This one can.
Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.
Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpoints
rank 90 = 40 + 25 + 0 + 19 + 6
rank@v1 · act now
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.99999 · CISA KEV listed · without this subject the record ranks 50
What it costs you if it fires
NVD CVSS base score, then the CNA's own
CVSS 10.0, from NVD · without this subject the record ranks 65
It is getting worse, not staying still
FIRST EPSS series, rescorings and bad loads removed
no persisting rise in 365 days · without this subject the record ranks 90
How much of the world it touches
NVD CPE configurations
323 products in the CPE ranges · without this subject the record ranks 71
Someone else already set the date
CISA KEV remediation due date
CISA remediation date held · without this subject the record ranks 84
Hindsight · the state
Foresight · where to check next
log4j2 is one instance of CWE-502, deserialization of untrusted data. The index holds 3512 prior instances of this class, 75 KEV-listed. 6 neighbors share the mechanism; each carries its own record state. taxonomy@v1
Running Apache Log4j2? Check your version
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Set up a watchlist (free with an account: one stack of three products)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.
Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Show full CISA required action
For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks. Temporary mitigations using one of the measures provided at https://www.cisa.gov/uscert/ed-22-02-apache-log4j-recommended-mitigation-measures are only acceptable until updates are available.
Exploit Status & Known PoCs a ladder, not a score
Current rung: Ransomware campaign use known, 2021-12-10.
Affected & Fixed Versions as published
Show all 323 published ranges
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
$4.99M = $4.99M incident cost x 1 exposure x 0.99999 likelihood
udv@v1 · unaudited · wrong for you until you say what you run
$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.
What it is stated by the CNA
Log4Shell is the common name for CVE-2021-44228. 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. cve-aliases@2026-08-27
Read the rest of the CNA's description
Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
NVD's analysis a second authority
- severity
- 10 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- weakness
- CWE-20; CWE-400; CWE-502; CWE-917
- affected versions
- apache log4j >= 2.0.1 < 2.3.1; apache log4j >= 2.4.0 < 2.12.2; apache log4j >= 2.13.0 < 2.15.0; and 320 more, listed in full below
- also scored by
- 10 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
check it yourself logging.apache.org openwall.com openwall.com tools.cisco.com openwall.com security.netapp.com +14 morereceipt
Dated events
Movement the material steps
This score more than doubled inside 72 hours. Both observations are in the full history below.
Show all 109 observations
109 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
The full biography
Listed by CISA on the day it published, exploit probability more than doubled between 2021-12-13 and 2021-12-14 (0.18794 → 0.50253) and the record had been public for 4 years, 8 months when this index was last written.
No material movement in 81 days as of the last ingest this index recorded.
The pattern, elsewhere
log4j2 is one instance of CWE-502, deserialization of untrusted data. The index holds 3512 prior instances of this class, 75 KEV-listed. 6 neighbors share the mechanism; each carries its own record state. cwe-consequences@4.20
3512 records in this class held. The six above are ranked by exploit maturity, then recency.
Siblings and hubs
Records related to this one
Its defect family
apache software foundation apache log4j2
Of the 3 records in this family, this is the only one with public proof-of-concept code, and it holds 418 references to it.
Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.
Family membership: held values
This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.
Browse the index from here
These are index-wide views, not findings about CVE-2021-44228.
What usually comes next
Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.