CVE-2021-45105: Uncontrolled Recursion Denial of Service in Apache Log4j2
- Vendors
- SonicwallOracle CorporationNetAppDebian ProjectApache Software Foundation
Apache Log4j2 versions 2.0-alpha1 through 2.16.0, excluding 2.12.3 and 2.3.1, fail to prevent uncontrolled recursion during evaluation of self-referential lookups. When a non-default Pattern Layout contains a Context Lookup, an attacker controlling Thread Context Map data can supply a crafted value that triggers recursive lookup evaluation. This can produce a StackOverflowError and terminate the affected application process, causing denial of service.
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 can disrupt application availability by exhausting the execution stack and terminating the affected process. This vulnerability does not itself establish remote code execution, information disclosure, or integrity compromise; those impacts associated with other Log4j vulnerabilities should not be attributed to CVE-2021-45105.
Mitigation
If you can’t patch tonight, do this now.
If immediate upgrading is not possible, replace Context Lookups in PatternLayout with Thread Context Map conversion patterns such as %X, %mdc, or %MDC. Alternatively, remove Context Lookup references that resolve externally controlled values, including HTTP headers and other user input. Do not rely on message-lookup disabling flags or removal of JNDI lookup functionality as a fix for this recursive Context Lookup vulnerability.
Remediation
Patch, then assume compromise.
Upgrade Log4j to a supported release containing the fix. The first fixed versions are 2.17.0 for Java 8 or later, 2.12.3 for Java 7, and 2.3.1 for Java 6. For applications bundling Log4j, install the vendor's corresponding fixed product release or security patch. Updating Java alone does not remediate the vulnerable Log4j library. If log4j-api is used alongside log4j-core, keep their versions aligned.
Exploits
3 exploits validated by Mallory's analysis. Hidden: 8 rejected by Mallory's analysis as not a working exploit.
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-45105 exploited in the wild?
- Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2021-45105?
- Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2021-45105, the earliest disclosed Apr 3, 2022.
- Is there a patch for CVE-2021-45105?
- Upgrade Log4j to a supported release containing the fix. The first fixed versions are 2.17.0 for Java 8 or later, 2.12.3 for Java 7, and 2.3.1 for Java 6.
- What products are affected by CVE-2021-45105?
- Apache Software Foundation Log4j, Sonicwall 6bk1602-0aa12-0tp0 Firmware, Sonicwall 6bk1602-0aa22-0tp0 Firmware, Sonicwall 6bk1602-0aa32-0tp0 Firmware, Sonicwall 6bk1602-0aa42-0tp0 Firmware, and at least 112 more.
- How severe is CVE-2021-45105?
- CVE-2021-45105 has a CVSS v3.1 score of 5.9 (Medium) and an EPSS score of 100.0% (100th percentile) as of Nov 4, 2026.
Recent activity
67 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.