Log4Shell RCE in Apache Log4j Exposes Java Applications
Vulnerability Disclosure · 3 sources · Updated 3mo ago · First seen Aug 28, 2026

Apache Log4j 2’s JNDI lookup feature enabled the critical Log4Shell remote-code-execution vulnerability, tracked as CVE-2021-44228. An attacker could cause a vulnerable application to log a crafted string that triggers a lookup to an attacker-controlled LDAP or other JNDI service, potentially leading to arbitrary code execution under the application’s privileges. The issue affected Log4j 2 versions from 2.0-beta9 through 2.14.1 and created broad exposure because Log4j is widely embedded in Java software and services.
Organizations should identify direct and transitive Log4j dependencies, upgrade to a supported remediated release appropriate to their Java runtime, and verify that deployed artifacts—not only build manifests—no longer contain vulnerable log4j-core versions. SLF4J itself is not vulnerable: it is a logging facade and does not perform Log4j’s JNDI message lookups, though applications using SLF4J can remain exposed when their selected logging backend is vulnerable Log4j 2. Internet-facing Java services and vendor-supplied products should be prioritized for patching, monitoring, and vendor confirmation.


