Koffei

CVE-2021-44228

🟠 Medium In CISA KEV

Apache Log4j 2 (log4j-core). The exposure is transitive: the risk is rarely Log4j installed directly, but Log4j bundled inside something else, which is why inventories built from installed products missed it · 2.0-beta9 through 2.14.1, excluding the security releases 2.3.1, 2.12.2 and 2.12.3. Message lookup substitution was disabled by default in 2.15.0 and the JNDI lookup removed in 2.16.0

CVSS (Koffei note)
10.0
CVSS (v3.1, CVE List)
10.0
EPSS (2026-11-18)
99.999%
100.00th percentile
CISA KEV
2021-12-10
due 2021-12-24

Exploitation

Yes — CISA KEV since 10/12/2021, SSVC exploitation active, automatable yes, technical impact total (recorded 04/02/2025). In KEV on the day the CVE was published, 10/12/2021, which no other row in this report matches. Exploitation is still measurable years later: a longitudinal study from a network telescope, read for this row, covers December 2021 to October 2025 and concludes that exploitation persists for several years after disclosure, concentrated in a shrinking set of recurring scanner and callback infrastructures with increasing payload obfuscation. It publishes no volume figures, and its data ends in October 2025, so it evidences a long tail and not activity inside the 60-day window. Not dated inside this report's 60-day window: nothing read for this row evidences exploitation after that study's measurement window, which ends in October 2025, and the fix has been available for years, so this is 🟠 and not 🔴 under the recency rule. Neither CISA KEV nor its JSON feed could be reached in this run, so the KEV date comes from the record's CISA-ADP container. Existing PoC (not opened), recorded from the proof-of-concept list supplied on 09/11/2026. For Log4Shell this adds nothing to the exploitation picture, which is already KEV-confirmed and measured ; it is recorded for completeness. 16/11/2026 addition, rating kept 🟠: Kaspersky ICS CERT (report 05/11/2026, read through The Hacker News of 16/11/2026) documents BO Team (Black Owl, Hoody Hyena, Lifting Zmiy) using this flaw on a VMware vCenter 7.0.3 server for a root shell during a months-long intrusion at a Russian software developer, which contacted Kaspersky in June 2025. That dates the exploitation to about mid-2025, outside the 60-day window, so it adds a named actor but does not lift the row to 🔴

Timeline

  1. 10/12/2021Added to the CISA KEV catalogue
  2. 10/12/2021CVE record published (CVE List)
  3. 24/12/2021CISA deadline for US federal agencies
  4. 16/11/2026BO Team used Log4Shell on vCenter to own a Russian software maker for months

Relationships

Apache Software FoundationApache Software FoundationBO TeamBO TeamCVE-2021-44228CVE-2021-44228

exploits suspected named in the same story vendor · Select a box to open its page · All relationships

Risk

10.0 Critical (v3.1, scored by CISA-ADP ; the Apache CNA recorded only the word critical, with no vector) — AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, EPSS 99.999% (100.00th percentile, scored 05/11/2026). The CNA assigned three CWEs, which is rare and tells you how many ways it bites: CWE-502 deserialization of untrusted data, CWE-400 uncontrolled resource consumption and CWE-20 improper input validation. Known publicly as Log4Shell

Fix

Yes — 2.17.1 is the version to be on for this and the follow-on flaws (CVE-2021-44790 is already in this note). 2.15.0 and 2.16.0 were both superseded within days

Official description

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 messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

CWE-20,CWE-400,CWE-502