Exploited CVEs / Apache / CVE-2021-44228

CVE-2021-44228

Patch immediately
Exploited in the wild and used in ransomware campaigns.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Move this ahead of everything else in the queue, then verify the fix actually landed on every exposed device.

Actively exploited Apache Log4j2 vulnerability, Critical severity, CVSS 10.0. Added to the CISA KEV catalog 2021-12-10.

All about CVE-2021-44228: the Senserva AI read, the CISA required action and deadline, the official fix, and the questions admins ask.

Which of your devices are still exposed? Find out free with a full Microsoft 365 audit.

Senserva AI read on CVE-2021-44228CISA required actionOfficial fix for CVE-2021-44228Admin questions#83 hottest CVE right now

Apache Log4j2 Remote Code Execution Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted, and the vulnerability is known to be used in ransomware campaigns. Federal agencies were required to remediate by 2021-12-24 (that deadline has passed); treat that date as the outer bound for your own environment. Check the vendor security advisory for the fix.

CriticalCISA KEVRansomware

Risk summary

CVSS base
10.0
EPSS exploit probability
100%
Severity
Critical
Added to KEV
2021-12-10
CISA due date
2021-12-24 (past due)

Senserva AI Opinion for CVE-2021-44228

Apache Log4j2's JNDI flaw is the rare CVSS 10.0 vulnerability, trivially exploitable in any application that logs attacker-influenced strings, which described an enormous share of enterprise Java software. Exploitation has run continuously since December 2021, including ransomware campaigns, and the hardest problem remains inventory: Log4j2 hides inside vendor appliances and applications where admins cannot see it. Its 100% EPSS score reflects exploitation that never stopped.

Do this: Run dependency and appliance scans for embedded Log4j2 rather than trusting past remediation, and patch or mitigate every instance found.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2021-44228

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

Full tracking and change history for CVE-2021-44228

Published
2021-12-10
Last revised
2021-12-10
Changes tracked
1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

CISA required action

Federal (BOD 22-01) remediation due date: 2021-12-24 (past due).

For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks. Temporary mitigations using one of the measures provided at https://www.cisa.gov/uscert/ed-22-02-apache-log4j-recommended-mitigation-measures are only acceptable until updates are available.

Official fix for CVE-2021-44228

Check the vendor's security advisory channel for the patched Log4j2 versions and workarounds.

Common questions about CVE-2021-44228

Is CVE-2021-44228 actively exploited?

Yes. CVE-2021-44228 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2021-12-10, which means exploitation in the wild has been confirmed, not predicted. Its EPSS 30-day exploitation probability is 100%. CISA also reports it is known to be used in ransomware campaigns.

What is the CISA deadline and required action for CVE-2021-44228?

CISA set the federal (BOD 22-01) remediation due date at 2021-12-24, which has passed; treat any unremediated system as overdue. The verbatim required action: For all affected software assets for which updates exist, the only acceptable remediation actions are: 1) Apply updates; OR 2) remove affected assets from agency networks. Temporary mitigations using one of the measures provided at https://www.cisa.gov/uscert/ed-22-02-apache-log4j-recommended-mitigation-measures are only acceptable until updates are available.

What fixes CVE-2021-44228?

Check the vendor's security advisory for the patched Log4j2 versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.

Can I ask my own AI about CVE-2021-44228?

Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2021-44228's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed three times a day (5 AM, 12:30 PM, and 7 PM US Central).

More exploited Apache CVEs

The newest Apache entries on the CISA KEV catalog:

All Apache exploited CVEs on one page: Apache vulnerabilities actively exploited.

Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.

One Free Unlimited Audit: all users, all settings, all patches, all tenants. All you do is register.

One free audit, across every tenant you manage: 1 scan to find, 2 to review your fixes. It finds:

Lexicon: the terms on this page
CVE
Common Vulnerabilities and Exposures. A unique ID for one publicly known vulnerability, such as CVE-2025-1234.
KB
Microsoft Knowledge Base article. The identifier for a specific Microsoft update.
KEV
CISA Known Exploited Vulnerabilities. CVEs confirmed exploited in the wild. Fix these first.
CVSS
Common Vulnerability Scoring System. A standardized Severity score from 0 to 10.
EPSS
Exploit Prediction Scoring System. The probability a CVE will be exploited in the next 30 days.
MSRC
Microsoft Security Response Center. Microsoft's Patch Tuesday advisories and KB-to-CVE mapping.
NVD
National Vulnerability Database (NIST). Authoritative CVE metadata and CVSS scores.
Ransomware
The vulnerability is linked to known ransomware activity.
Reference: Microsoft CVE and vulnerability management, the full CVE-to-patch lookup ranked by real-world risk, and the Microsoft patching guide, how Intune, Windows Autopatch, Defender, and Azure Update Manager fit together.
Data notice: this page, the feeds, and the API are provided as is, for informational purposes only, without warranty of any kind. Senserva, LLC does not guarantee the accuracy, completeness, or timeliness of third-party data (MSRC, NVD, CISA KEV, EPSS) and accepts no liability for actions taken based on it; verify against the authoritative vendor advisory before acting. Built daily with Senserva Trustworthy AI. All use of this data is subject to the Senserva EULA.