CVE-2021-45046
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.
Scoring
- Severity
- CRITICAL
- CVSS base score
- 9
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
- EPSS probability
- 94.34%
- CISA KEV
- Known exploited vulnerability
- CWE
- CWE-917
- Published
- 2021-12-14
- Last modified
- 2026-09-16
Affected products
- Apache Software Foundation Apache Log4j
Weakness type
Related vulnerabilities
- CVE-2025-41243 — Spring Expression Language property modification using Spring Cloud Gateway Server WebFlux
- CVE-2025-3322 — Improper Neutralization of Special Elements in OnlineSuite
- CVE-2023-41331 — SOFARPC Remote Command Execution (RCE) Vulnerability
- CVE-2023-51593 — Voltronic Power ViewPower Pro Expression Language Injection Remote Code Execution Vulnerability
- CVE-2022-23463 — SpEL Injection in Nepxion Discovery
- CVE-2024-51466 — IBM Cognos Analytics expression language injection
- CVE-2023-42658 — InSpec Archive Command Vulnerable to Maliciously Crafted Profile
- CVE-2025-11175 — DiscussionTools should use better regex