Critical Log4Shell RCE in Apache Log4j Triggered Internet-Wide Exploitation
Active Exploitation · 47 sources · Updated 3mo ago · First seen May 24, 2026

A critical remote code execution flaw in Apache Log4j, tracked as CVE-2021-44228 and widely known as Log4Shell, exposed a vast range of Java applications and services to unauthenticated compromise through the library’s JNDI lookup feature. Security reporting said the bug affected Log4j versions 2.0-beta9 through 2.14.1, with early warnings surfacing through attacks against Minecraft servers before researchers and vendors confirmed broader exposure across enterprise software, cloud services, and Apache frameworks including Struts2, Solr, Druid, Flink, and Kafka. Researchers also warned that exploitation could lead not only to remote code execution but also to leakage of sensitive environment data such as cloud credentials and developer secrets.
Exploit code was released publicly and was quickly followed by heavy Internet-wide scanning and attack activity, including targeting of VMware vCenter Server, where VMware confirmed exploitation attempts in the wild and urged immediate mitigation. CISA described the flaw as one of the most serious vulnerabilities in recent memory and warned that hundreds of millions of devices could be affected, with likely follow-on abuse by cryptominers, ransomware operators, and other threat actors. Apache responded with a series of Log4j updates, including releases such as 2.12.2, 2.12.3, 2.12.4, and 2.3.1, while defenders published detection content and scanning tools as organizations raced to identify vulnerable systems and reduce exposure.


