Skip to content
Noroxi
NVD / CVE Program· CNA apache

CVE-2021-45046: Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attack

CriticalCVSS 9.0 · v3.1KEVWeaponized Fix available

Noroxi assessment

Priority: Now (action score 96/100)

  • CISA has confirmed exploitation in the wild (May 1, 2023); it is known to be used in ransomware campaigns. Remediation deadline for US federal agencies: May 22, 2023.
  • A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
  • Probability of exploitation in the next 30 days: 99.9% (FIRST EPSS); higher than 99.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: apache-log4j2 (Debian:10) 2.16.0-1~deb10u1; apache-log4j2 (Debian:11) 2.16.0-1~deb11u1; apache-log4j2 (Debian:12) 2.16.0-1.
  • Mentioned 6 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Patch today or shut off access. Upgrade to apache-log4j2 (Debian:10) 2.16.0-1~deb10u1; apache-log4j2 (Debian:11) 2.16.0-1~deb11u1; apache-log4j2 (Debian:12) 2.16.0-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS

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.

Published
Dec 14, 2021
Updated
Jun 17, 2026
EPSS
99.9% · 99th percentile

Report tools

JSON

Action score

96

Now

Patch today or shut off access.

CVSS
36 / 40 · 9.0 / 10
CISA KEV
30 / 30 · Listed
EPSS
30 / 30 · 99.9%

CISA SSVC decision

Exploitation
active
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on May 1, 2023. That signals real attacks, not theory.

Remediation deadline for US federal agencies: May 22, 2023.

Known to be used in ransomware campaigns.

Get told when this record changes

  • In CISA KEV: exploitation in the wild confirmed
  • Weaponized exploit exists
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2021-45046

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
apachelog4j
cvatcomputer vision annotation tool
intelaudio development kit
inteldatacenter manager
intelgenomics kernel library
inteloneapi
intelsecure device onboard
intelsensor solution firmware development kit
intelsystem debugger
intelsystem studio
siemenssppa-t3000 ses3000 firmware
siemenssppa-t3000 ses3000

and 49 more

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache Log4j

    • Apache Log4j2 and later · before 2.16.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:10apache-log4j2before 2.16.0-1~deb10u12.16.0-1~deb10u1
Debian:11apache-log4j2before 2.16.0-1~deb11u12.16.0-1~deb11u1
Debian:12apache-log4j2before 2.16.0-12.16.0-1
Mavenorg.apache.logging.log4j:log4j-corefrom 2.13.0 · before 2.16.02.16.0
Mavenorg.apache.logging.log4j:log4j-corefrom 2.4.0 · before 2.12.22.12.2
Mavenorg.apache.logging.log4j:log4j-corebefore 2.3.12.3.1
Mavenorg.ops4j.pax.logging:pax-logging-log4j2from 1.10.0 · before 1.10.81.10.8
Mavenorg.ops4j.pax.logging:pax-logging-log4j2from 1.11.0 · before 1.11.111.11.11
Mavenorg.ops4j.pax.logging:pax-logging-log4j2from 1.8.0 · before 1.9.21.9.2
Mavenorg.ops4j.pax.logging:pax-logging-log4j2from 2.0.0 · before 2.0.122.0.12
openSUSE:Leap 15.2disruptorbefore 3.4.4-lp152.2.3.13.4.4-lp152.2.3.1
openSUSE:Leap 15.2jakarta-servletbefore 5.0.0-lp152.2.15.0.0-lp152.2.1
openSUSE:Leap 15.2log4jbefore 2.16.0-lp152.3.9.12.16.0-lp152.3.9.1
openSUSE:Leap 15.3disruptorbefore 3.4.4-3.3.13.4.4-3.3.1
openSUSE:Leap 15.3jakarta-servletbefore 5.0.0-5.3.15.0.0-5.3.1
openSUSE:Leap 15.3log4jbefore 2.16.0-4.10.12.16.0-4.10.1
openSUSE:Leap 15.3log4jbefore 2.13.0-4.6.12.13.0-4.6.1
openSUSE:Tumbleweedlog4jbefore 2.16.0-2.12.16.0-2.1
Red Hat:jboss_enterprise_application_platform_eus:7.1::el7eap7-apache-cxfbefore 0:3.1.16-4.redhat_00003.1.ep7.el70:3.1.16-4.redhat_00003.1.ep7.el7
Red Hat:jboss_enterprise_application_platform_eus:7.1::el7eap7-apache-cxf-rtbefore 0:3.1.16-4.redhat_00003.1.ep7.el70:3.1.16-4.redhat_00003.1.ep7.el7
Red Hat:jboss_enterprise_application_platform_eus:7.1::el7eap7-apache-cxf-servicesbefore 0:3.1.16-4.redhat_00003.1.ep7.el70:3.1.16-4.redhat_00003.1.ep7.el7
Red Hat:jboss_enterprise_application_platform_eus:7.1::el7eap7-apache-cxf-toolsbefore 0:3.1.16-4.redhat_00003.1.ep7.el70:3.1.16-4.redhat_00003.1.ep7.el7
Red Hat:jboss_enterprise_application_platform_eus:7.1::el7eap7-jackson-databindbefore 0:2.8.11.6-2.SP1_redhat_00002.1.ep7.el70:2.8.11.6-2.SP1_redhat_00002.1.ep7.el7
Red Hat:jboss_enterprise_application_platform_eus:7.1::el7eap7-jettisonbefore 0:1.3.8-2.redhat_00002.1.ep7.el70:1.3.8-2.redhat_00002.1.ep7.el7

+66

Other highest-scoring records for the same primary product.

  • CVE-2021-44228Apache Log4j2 JNDI features do not protect against attacker controlled LDAP and other JNDI related endpointsKEV
    100Now
  • CVE-2017-5645In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another…
    66This week
  • CVE-2019-17571Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely…
    60This week

Published before and after this one in the same product

  • ← EarlierCVE-2020-9488Apr 27, 2020 · Improper validation of certificate with host mismatch in Apache Log4j SMTP appender.
    16Monitor
  • ← EarlierCVE-2021-4104Dec 14, 2021 · Deserialization of untrusted data in JMSAppender in Apache Log4j 1.2
    54Plan
  • Later →CVE-2021-45105Dec 18, 2021 · Apache Log4j2 does not always protect from infinite recursion in lookup evaluation
    53Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:apache-log4j22.16.0-1 · Debian:12Package registry (OSV)
Maven:org.apache.logging.log4j:log4j-core2.12.2Package registry (OSV)
Maven:org.apache.logging.log4j:log4j-core2.16.0Package registry (OSV)
Maven:org.apache.logging.log4j:log4j-core2.3.1Package registry (OSV)
Maven:org.ops4j.pax.logging:pax-logging-log4j21.10.8Package registry (OSV)
Maven:org.ops4j.pax.logging:pax-logging-log4j21.11.11Package registry (OSV)
Maven:org.ops4j.pax.logging:pax-logging-log4j21.9.2Package registry (OSV)
Maven:org.ops4j.pax.logging:pax-logging-log4j22.0.12Package registry (OSV)
opensuse:disruptor3.4.4-lp152.2.3.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:jakarta-servlet5.0.0-lp152.2.1 · openSUSE:Leap 15.2Package registry (OSV)
opensuse:log4j2.16.0-lp152.3.9.1 · openSUSE:Leap 15.2Package registry (OSV)
red hat:eap7-jackson-databind0:2.8.11.6-2.SP1_redhat_00002.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
red hat:eap7-log4j0:2.17.1-1.redhat_00001.1.el7eap · Red Hat:jboss_enterprise_application_platform:7.4::el7Package registry (OSV)
red hat:eap7-resteasy0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
red hat:eap7-resteasy-atom-provider0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
red hat:eap7-resteasy-cdi0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
red hat:eap7-resteasy-client0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
red hat:eap7-resteasy-crypto0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
red hat:eap7-resteasy-jackson-provider0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
red hat:eap7-resteasy-jackson2-provider0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
red hat:eap7-resteasy-jaxb-provider0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
red hat:eap7-resteasy-jaxrs0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)
red hat:eap7-resteasy-jettison-provider0:3.0.27-1.Final_redhat_00001.1.ep7.el7 · Red Hat:jboss_enterprise_application_platform_eus:7.1::el7Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Metasploit module ×1
  • Nuclei detection template ×3
  • Proof-of-concept repository on GitHub ×11

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHub11 repositories2021-12-15 → 2025-07-23
Metasploit moduleauxiliary/scanner/http/log4shell_scannerLog4Shell HTTP Scannerauxiliary2021-12-09
Nuclei detection templateNuclei template CVE-2021-45046-DAST —
Nuclei detection templateNuclei template CVE-2021-45046 —
Nuclei detection templateNuclei template vrealize-operations-log4j-rce —

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Metasploit-6 d
  2. Published
  3. First PoCsame day
  4. CISA KEV+502 d
  5. TodayNov 14, 2026+1795 d

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records