Skip to content

CVE-2021-45046

Apache Log4j2 Deserialization of Untrusted Data Vulnerability

  • Actively exploited
  • Used by ransomware
  • Critical · 9.0 of 10
Exploited since
1 May 2023
added to the CISA list
Chance of attacks
over 99.9%
in the next 30 days (FIRST EPSS)
Fix deadline
22 May 2023
for US federal agencies
Published
14 Dec 2021
in the NVD

What this means

Apache Log4j2 contains a deserialization of untrusted data vulnerability due to the incomplete fix of CVE-2021-44228, where the Thread Context Lookup Pattern is vulnerable to remote code execution in certain non-default configurations.

CISA

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.

NIST National Vulnerability Database

What to do

Apply updates per vendor instructions.

CISA's required action. If you use the product, install the vendor's update as soon as possible.

Affected

  • Apache Software Foundation Apache Log4j

Official sources

Data from the NIST National Vulnerability Database, the CISA Known Exploited Vulnerabilities list, FIRST EPSS and ENISA, checked 18 Nov 2026. CVSS vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H.

May we count your visit with Google Analytics? It sets cookies only if you accept. Privacy Policy