Skip to main content
Mallory
← Back to News
actively-exploited-vulnerabilityopen-source-dependency-vulnerabilityrapid-weaponizationproof-of-concept-release

Critical Log4Shell RCE in Apache Log4j Triggered Internet-Wide Exploitation

Active Exploitation · 47 sources · Updated 3mo ago · First seen May 24, 2026

Critical Log4Shell RCE in Apache Log4j Triggered Internet-Wide Exploitation

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.

This is being exploited nowSee which actors are running it and whether you're in range.
Check your exposure
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

20 events · Nov 30, 2021 – Feb 12, 2022
  1. Feb 12, 20225y ago

    Neo23x0 publishes log4shell-detector on GitHub

    By 2022-02-12, Neo23x0 had published log4shell-detector on GitHub, a tool for detecting Log4Shell exploitation attempts. The release added another public defensive utility aimed at helping responders identify signs of compromise related to Log4j attacks.

    GitHub - Neo23x0/log4shell-detector: Detector for Log4Shell exploitation attempts · GitHub
  2. Dec 29, 20215y ago

    Apache publishes further maintenance fixes in 2.12.4 and 2.3.1

    By late December 2021, Apache released additional Log4j updates including versions 2.12.4 and 2.3.1 for supported branches. These releases represented continued hardening and cleanup after the initial Log4Shell emergency and related vulnerabilities.

  3. Dec 28, 20215y ago

    Apache releases Log4j 2.12.3 to address follow-on issues

    Apache published Log4j 2.12.3 as an additional update after the initial emergency fixes, reflecting continued remediation for newly identified issues related to the Log4Shell response. This showed that patching guidance was evolving rapidly as researchers analyzed the flaw further.

  4. Dec 24, 20215y ago

    Fox-IT publishes Log4Shell PCAPs and network coverage resources

    On 2021-12-24, Fox-IT published a GitHub repository containing Log4Shell packet captures and network detection coverage material. The release provided defenders with technical artifacts to study exploit traffic and improve detection of Log4Shell-related activity.

    GitHub - fox-it/log4shell-pcaps: Log4Shell PCAPS and Network Coverage · GitHub
  5. Reported Dec 19, 20215y ago

    Red Hat fixes incomplete Log4j mitigation in OpenShift Metering Hive

    Red Hat identified CVE-2021-4125 after finding that the original Log4j mitigations in OpenShift Metering Hive containers had not removed all JndiLookup.class files. Hive project patches and Red Hat advisories RHSA-2021:5183, RHSA-2021:5184, and RHSA-2021:5186 remediated affected OpenShift Container Platform 4.8, 4.7, and 4.6 deployments.

    2033121 - (CVE-2021-4125) CVE-2021-4125 kube-reporting/hive: Incomplete fix for log4j CVE-2021-44228 and CVE-2021-45046
  6. Dec 18, 20215y ago

    Amazon Corretto publishes Log4j hotpatch agent

    Amazon Corretto released an open-source Java agent on GitHub to hotpatch CVE-2021-44228 in vulnerable Log4j 2 applications. The tool provided an additional mitigation option for organizations that could not immediately deploy full Apache Log4j updates.

    GitHub - corretto/hotpatch-for-apache-log4j2: An agent to hotpatch the log4j RCE from CVE-2021-44228. · GitHub
  7. Dec 16, 20215y ago

    Red Hat fixes Log4j 1.x CVE-2021-4104 in OpenShift 4.7.40

    On 2021-12-16, Red Hat issued critical advisory RHSA-2021:5184 for OpenShift Container Platform 4.7.40. The update remediated CVE-2021-4104, which could permit remote code execution when a Log4j 1.x application used JMSAppender, for RHEL 8 deployments on x86_64, Power, and IBM Z/LinuxONE.

    RHSA-2021:5184 - Security Advisory - Red Hat Customer Portal
  8. Reported Dec 14, 20215y ago

    CVE-2021-45046 disclosed as follow-on Log4j vulnerability

    Red Hat documented CVE-2021-45046, affecting Log4j 2.0 through 2.15.0 in certain non-default Pattern Layout configurations using Context Lookups. The prior CVE-2021-44228 mitigation was insufficient in many such cases; Log4j 2.16.0 removed message lookup patterns and disabled JNDI by default to resolve the issue.

    CVE-2021-45046 - Red Hat Customer Portal
  9. Dec 14, 20215y ago

    Red Hat issues Log4Shell fixes for affected products

    On 2021-12-14, Red Hat issued fixed errata and mitigation guidance for CVE-2021-44228 affecting products including OpenShift Logging, AMQ Streams, Data Grid, Fuse, and Integration. The advisory also documented interim mitigations such as disabling message lookups or removing the JndiLookup class.

    CVE-2021-44228 - Red Hat Customer Portal
  10. Dec 14, 20215y ago

    SolarWinds publishes Log4Shell security advisory

    SolarWinds published a Trust Center security advisory for CVE-2021-44228, documenting the company's assessment of Log4Shell impact on its products and providing remediation guidance. This marked an official vendor response from another major enterprise software supplier during the broader industry-wide mitigation effort.

    SolarWinds Trust Center Security Advisories | CVE-2021-44228 | SolarWinds
  11. Dec 14, 20215y ago

    Northwave Security publishes Log4Shell checking script

    On 2021-12-14, Northwave Security published log4jcheck on GitHub, a script designed to identify potentially vulnerable Log4j systems by injecting Log4Shell payloads into common HTTP headers. The release added a public technical tool for defenders to test exposure during the early response period.

    GitHub - NorthwaveSecurity/log4jcheck: A script that checks for vulnerable Log4j (CVE-2021-44228) systems using injection of the payload in common HTTP headers. · GitHub
  12. Dec 14, 20215y ago

    VMware confirms in-the-wild exploitation attempts against vCenter

    VMware said it had confirmed exploitation attempts in the wild affecting VMware vCenter Server and urged customers to patch, apply workarounds, or remove Internet exposure. The advisory underscored the immediate enterprise impact of Log4Shell on widely deployed infrastructure software.

  13. Dec 13, 20215y ago

    CISA warns Log4Shell may affect hundreds of millions of devices

    On 2021-12-13, CISA Director Jen Easterly called Log4Shell one of the most serious vulnerabilities of her career and warned that hundreds of millions of devices could be affected. CISA said broad exploitation was likely, including by ransomware and cryptomining actors, and began coordinating public guidance with international partners.

  14. Dec 11, 20215y ago

    Germany's BSI raises Log4Shell cyber warning to red

    On 2021-12-11, Germany's Federal Office for Information Security (BSI) raised its cyber warning level to red over Log4Shell, calling it an extremely critical threat. BSI reported mass scanning, attempted and early successful compromises, including cryptominer, botnet, and initial ransomware activity, and urged rapid patching and mitigations.

    BSI - Presse - Update: Warnstufe Rot: Schwachstelle Log4Shell führt zu extrem kritischer Bedrohungslage (archiviert)
  15. Dec 10, 20215y ago

    Elastic publishes advisory for Log4Shell impact on Elastic Stack

    On 2021-12-10, Elastic issued security advisory ESA-2021-31 addressing CVE-2021-44228 and detailing the impact on Elastic Stack products. The company provided product-specific mitigation and remediation guidance, marking an official vendor response for a widely deployed enterprise platform.

    Apache Log4j2 Remote Code Execution (RCE) Vulnerability - CVE-2021-44228 - ESA-2021-31 - Announcements / Security Announcements - Discuss the Elastic Stack
  16. Dec 10, 20215y ago

    Researchers observe heavy exploitation and scanning activity

    In the days following exploit publication, defenders reported widespread attack traffic, including scanning and exploitation attempts at high volume against exposed systems. Reporting described more than 100 attacks per minute, with activity coming from both researchers and malicious actors.

  17. Dec 10, 20215y ago

    Apache releases initial Log4j fixes for CVE-2021-44228

    Apache published updated Log4j releases to address CVE-2021-44228, including the 2.12.2 branch release. These releases were part of the first wave of remediation guidance for vulnerable Log4j 2 deployments.

  18. Dec 9, 20215y ago

    Log4Shell draws attention through Minecraft abuse warnings

    On 2021-12-09, warnings to Minecraft users highlighted that malicious chat messages could trigger code execution on vulnerable Java-based Minecraft servers and clients. This helped reveal that the issue affected far more than Minecraft because Log4j was embedded in many enterprise applications and frameworks.

  19. Dec 9, 20215y ago

    Public exploit code for Log4Shell begins circulating

    By 2021-12-09, proof-of-concept exploit code for CVE-2021-44228 had been published, enabling remote code execution via Log4j's JNDI lookup behavior. Security reporting also noted early Internet-wide scanning and exploitation attempts soon after disclosure.

  20. Nov 30, 20215y ago

    Apache proposes restricting LDAP access via JNDI in Log4j PR #608

    On 2021-11-30, Apache opened pull request #608 for Log4j 2 to restrict LDAP access via JNDI. The change reflects an early code-level mitigation effort tied to the vulnerability before the broader public disclosure and emergency release cycle.

    Restrict LDAP access via JNDI by rgoers · Pull Request #608 · apache/logging-log4j2 · GitHub
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Vulnerabilities

1 linked

Affected products

6 linked
Apache SolrAmazon Web ServicesIcloudSteamVmware Vcenter ServerVmware

Organizations

1 linked
Apache Software Foundation
Do you run this?Correlate live exploitation activity against the software you actually run, and see where you're exposed.
See Who's Exploiting This
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.