Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messa…
Evidence confidence: Campaign documented
● Hype ● Reality
Earlier evidence-support scores are retained in history; this chart shows only the current priority definition.
First record: hype 1.9 · reality 9.4 (2026-11-02 15:12). The curve appears once the score changes.
Public exploit entries / repo candidates
Reality is general threat/review priority, combining observed exploitation, CVSS severity and fresh EPSS. Evidence confidence is separate. This is not calibrated risk, a victim count or an asset-specific assessment. A range reflects missing numeric inputs.
Score evaluated: 2026-11-05 13:58:32.072469+00:00 · EPSS snapshot: 2026-11-05T12:03:04Z
Microsoft Defender observed Log4Shell exploitation followed by Khonsari ransomware execution.
Scope: Historical Microsoft telemetry, including compromised Minecraft clients; not evidence of a current campaign.
Attack observation: not dated; source reviewed 2026-11-02.
VMware documents its own NSX detection telemetry and post-exploitation payloads.
Scope: Historical NSX network telemetry distinguishes scanning from exploitation attempts; it does not quantify global compromises.
Attack observation: not dated; source reviewed 2026-11-02.