CVE-2021-44228: Log4Shell
- Vendors
- SiemensNetAppCisco SystemsIntel CorporationDebian ProjectSonicwallFedora ProjectApache Software Foundation
Log4Shell is a JNDI injection vulnerability in Apache Log4j 2 that can allow unauthenticated remote code execution when attacker-controlled text is logged. Vulnerable lookup processing interprets crafted log messages or parameters as JNDI expressions and contacts attacker-controlled LDAP or other naming-service endpoints, potentially retrieving and executing malicious Java code. Affected versions are 2.0-beta9 through 2.15.0, excluding security releases 2.12.2, 2.12.3, and 2.3.1. Message lookup substitution is disabled by default in 2.15.0, but that release's protections were incomplete. Message lookup functionality was removed in 2.16.0 and the corresponding security backports. The vulnerability affects log4j-core, not log4j-api alone, log4net, or log4cxx.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits arbitrary code execution with the privileges of the affected Java application, potentially compromising system confidentiality, integrity, and availability. Consequences include sensitive-data exfiltration, credential theft, malware deployment, service disruption, and subsequent lateral movement. Applications running with administrative or root privileges can expose the entire host; exploitation of vulnerable VMware vCenter deployments has been associated with root command-shell access. Attacker-triggered JNDI lookups can also disclose information even where runtime restrictions prevent remote code loading. Log4Shell has been actively exploited, including in ransomware campaigns.
Mitigation
If you can’t patch tonight, do this now.
If patching cannot be completed immediately, follow current product-specific vendor workarounds. Removing the JndiLookup class from every affected log4j-core archive and restarting the application is a documented temporary measure. On applicable Log4j 2.10+ deployments, setting the JVM property log4j2.formatMsgNoLookups=true can mitigate the original message-lookup vector, but is not a comprehensive defense against related incomplete-fix vulnerabilities and is insufficient in some product configurations. Restrict outbound connections from affected applications, segment vulnerable services, minimize their network exposure, and run them without elevated privileges. WAF and IPS signatures provide supplemental protection but do not replace patching.
Remediation
Patch, then assume compromise.
Upgrade affected applications and all direct, transitive, shaded, and bundled log4j-core dependencies to a current supported security release compatible with the runtime, then rebuild and redeploy affected artifacts. For third-party appliances and commercial software, apply vendor-supported product fixes rather than independently replacing libraries unless explicitly instructed. Do not stop at Log4j 2.15.0: its initial fix was incomplete. Historical remediation baselines covering the subsequent 2021 Log4j issues include 2.17.1 for Java 8+, 2.12.4 for Java 7, and 2.3.2 for Java 6; these are not substitutes for selecting a currently supported release. Restart affected services and verify that vulnerable library copies are no longer loaded.
Exploits
81 exploits validated by Mallory's analysis. Hidden: 170 rejected by Mallory's analysis as not a working exploit; 10 not yet analyzed, such as Exploit-DB entries; 1 not loaded here. Showing the 25 most capable, earliest first.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2021-44228 exploited in the wild?
- Yes. As of Nov 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Dec 10, 2021.
- Is there a public exploit for CVE-2021-44228?
- Yes. Mallory tracks 81 public exploits or proofs of concept for CVE-2021-44228, the earliest disclosed Dec 9, 2021.
- Is there a patch for CVE-2021-44228?
- Upgrade affected applications and all direct, transitive, shaded, and bundled log4j-core dependencies to a current supported security release compatible with the runtime, then rebuild and redeploy affected artifacts. For third-party appliances and commercial software, apply vendor-supported product fixes rather than independently replacing libraries unless explicitly instructed.
- What products are affected by CVE-2021-44228?
- Apache Software Foundation Log4j, Siemens 6bk1602-0aa12-0tp0 Firmware, Siemens 6bk1602-0aa22-0tp0 Firmware, Siemens 6bk1602-0aa32-0tp0 Firmware, Siemens 6bk1602-0aa42-0tp0 Firmware, and at least 140 more.
- How severe is CVE-2021-44228?
- CVE-2021-44228 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 100.0% (100th percentile) as of Nov 16, 2026.
Recent activity
727 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.