CVE-2021-45046Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attack
Updated under an hour ago ()
Does this affect you?
It affects Apache Software Foundation Apache Log4j and 55 other products. Add what you run to find out whether that includes you.
CISA lists it as known exploited since May 1, 2023; federal agencies had to remediate by May 22, 2023, and it is known to be used in ransomware. Treat that date as your deadline.
Do this next
Free account, 1 product
It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.
- CVSS
- 9.0 CRITICAL (v3.1, CISA ADP)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
- Weakness (CWE)
- CWE-917
- Known exploited
- Added to CISA KEV May 1, 2023; federal remediation due May 22, 2023; known ransomware useApply updates per vendor instructions.
- EPSS (exploitation in the next 30 days)
- 99.98% (percentile 100)
- Assigned by
- apache
- NVD analysis
- Analyzed
- Record last updated
- Oct 21, 2025
- First seen by InfoSec Signals
- Oct 9, 2026
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.