What it is
CVE-2021-45046 is an unauthenticated vulnerability affecting Apache Log4j. It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations.
Vulnerability report
Apache Log4j Denial of Service
Apache Log4j · affected before 2.16.0
Decision summary
Direct answers before the deeper technical record.
What it is
CVE-2021-45046 is an unauthenticated vulnerability affecting Apache Log4j. It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations.
Have exploitation attempts been observed?
Yes. Exploitation attempts have been reported for this vulnerability. Previdian lists it as a known exploited vulnerability. Listed in CISA KEV. Confidence is confirmed.
Who is affected?
Apache Log4j affected before 2.16.0.
What should we do?
Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.
Overview
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.
Exploitation evidence
Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.
CISA
A trusted third party reported exploitation attempts.
CISA
Exploitation attempts against this vulnerability are associated with malware-related payloads.
GitHub
Public scanner or PoC coverage increases practical exploitability.
Per-source evidence links for KEV attestations are available through the Previdian Pro API.
Learn about Pro API access| Source | Added |
|---|---|
| CISA First | 2023-05-01 00:00 UTC |
Detection
Make the evidence actionable in scanner, SOC, and edge-control workflows.
Nuclei template detected 25 Apr 2025.
View Nuclei template (opens in new tab)No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.
Learn about virtual patches →Scanner and exploit-framework references linked to this CVE.
| Scanner | Reference | Detected |
|---|---|---|
| Nuclei | https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2021/CVE-2021-45046.yaml | 25 Apr 2025 |
| Metasploit | https://github.com/rapid7/metasploit-framework/blob/master/modules/auxiliary/scanner/http/log4shell_scanner.rb | 09 Dec 2021 |
Risk and context
CVSS v3.1
Potential damage if exploited. Separate from whether attackers are using it.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
EPSS
100.0%
Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.
These PoCs are unverified and could contain malware. Use at your own risk.
nuclei · Created Unknown
Timeline
14:20 UTC
Public proof-of-concept code published
00:00 UTC
Scanner coverage available
00:00 UTC
Listed in the CISA Known Exploited Vulnerabilities catalog
00:00 UTC
Malware-related exploitation attempts or payloads reported
16:55 UTC
Vulnerability disclosed publicly
00:00 UTC
Identifier reserved by the CNA
00:00 UTC
Exploit module available
Pro API
Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.
GET /api/v2/pro/kevs/CVE-2021-45046
Sample API response{
"cve_id": "CVE-2021-45046",
"confidence": "Confirmed",
"cvss_score": 9.0,
"cvss_estimated": false,
"epss_score": 0.99977,
"exploit_status": {
"exploited_in_the_wild": true,
"active_exploitation_observed": false
},
"sensor_telemetry": { "attempts": 0, "sensors": 0 }
}