CVE-2021-45046: Log4Shell follow-up
Is CVE-2021-45046 real, exploitable, or a false positive? Here's the community verdict.
Community verdict: No field verdicts yet. Be the first practitioner to weigh in.
signals
public sources
Confirmed exploited in the wild. Patch this first, regardless of the base score.
cisa ssvc
CISA Vulnrichment · assessed
CISA decision, by how critical the affected system is to you:
- low impact → Track
- medium impact → Attend
- high impact → Act
Track: normal patch cycle · Track*: watch closely · Attend: patch sooner · Act: patch now. About SSVC ↗
public exploits
links to sources — we don’t host codeUnverified proof-of-concept code has been published. It may or may not be functional — assess before relying on it.
affected packages
GHSA-7rjr-3q55-vv33 · GitHub rates it critical- Mavenorg.apache.logging.log4j:log4j-core
- Vulnerable
- ≥ 2.13.0, < 2.16.0; ≥ 2.4.0, < 2.12.2; < 2.3.1
- Fixed in
- 2.16.0, 2.12.2, 2.3.1
- Mavenorg.ops4j.pax.logging:pax-logging-log4j2
- Vulnerable
- ≥ 1.8.0, < 1.9.2; ≥ 1.10.0, < 1.10.8; ≥ 1.11.0, < 1.11.11; ≥ 2.0.0, < 2.0.12
- Fixed in
- 1.9.2, 1.10.8, 1.11.11, 2.0.12
Source: GitHub Advisory Database (CC-BY 4.0), via OSV.dev. Check your lockfile version against the ranges above.
baseline read
auto · not a community verdict
Real — exploited in the wild
CISA confirms active exploitation. Treat scanner hits as true positives unless your specific version or config is unaffected.
Based on CISA KEV
Confirm or dispute →CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
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.
References
Published · Added to CISA KEV (503 days after publication)
Embed this verdict
[](https://www.truepositive.app/cve/CVE-2021-45046)<a href="https://www.truepositive.app/cve/CVE-2021-45046"><img src="https://www.truepositive.app/cve/CVE-2021-45046/badge.svg" alt="TruePositive verdict for CVE-2021-45046"></a>Live badge that updates automatically as the community verdict changes.
timeline
- CISA SSVC assessment · exploitation: active
- Added to CISA KEV · confirmed exploited in the wild
- Published by NVD
- Added to VulnCheck KEV · reported exploited in the wild
Score and exploit changes tracked since .
Community ground truth
Be the first practitioner to weigh in
So far this is only TruePositive's editorial baseline from public sources. Add your real-world verdict below — it becomes the signal the next person triaging this relies on.
🥇 The first 50 practitioners to contribute earn a Founding Contributor badge.
In your experience, is this finding real and exploitable?
awaiting field verdictsCurated baseline: TruePositive's read from public sources is Real & exploitable — a starting point, not a community verdict.
No account needed. Anonymous verdicts post as an unverified signal. Log in to make yours verified and earn reputation.
Field notes & remediation
Verdicts are the quick signal. Notes are the evidence and fixes behind them.
- 0
This is confirmed exploited in the wild. It is in the CISA KEV catalog, so attackers are actively using it, not just researchers. It is reachable over the network with no authentication and no user interaction, which is the most dangerous profile. Patch this on priority and confirm the fix holds.
Add a field note or remediationoptional
Related CVEs
Same weakness: CWE-917.
- CVE-2021-26084CRIT 9.8KEVEPSS 100%
In affected versions of Confluence Server and Data Center, an OGNL injection vulnerability exists that would allow an unauthenticated attacker to execute arbitrary code on a Confluence Server or Data Center instance. The affected versions are before version 6.13.23, from version 6.14.0 before 7.4.11, from version 7.5.0 before 7.11.6, and from version 7.12.0 before 7.12.5.
- CVE-2022-26134CRIT 9.8KEVEPSS 100%
In affected versions of Confluence Server and Data Center, an OGNL injection vulnerability exists that would allow an unauthenticated attacker to execute arbitrary code on a Confluence Server or Data Center instance. The affected versions are from 1.3.0 before 7.4.17, from 7.13.0 before 7.13.7, from 7.14.0 before 7.14.3, from 7.15.0 before 7.15.2, from 7.16.0 before 7.16.4, from 7.17.0 before 7.17.4, and from 7.18.0 before 7.18.1.
- CVE-2020-10199HIGH 8.8KEVEPSS 99%
Sonatype Nexus Repository before 3.21.2 allows JavaEL Injection (issue 1 of 2).
- CVE-2020-17530CRIT 9.8KEVEPSS 96%
Forced OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution. Affected software : Apache Struts 2.0.0 - Struts 2.5.25.
- CVE-2010-1871HIGH 8.8KEVEPSS 83%
JBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, does not properly sanitize inputs for JBoss Expression Language (EL) expressions, which allows remote attackers to execute arbitrary code via a crafted URL. NOTE: this is only a vulnerability when the Java Security Manager is not properly configured.
- CVE-2026-41729HIGH 8.1Real · low riskEPSS 0%
Spring Data REST is vulnerable to SpEL expression injection through map-typed properties when processing JSON Patch (application/json-patch+json) requests. When a persistent entity exposes a Map-typed property, the JSON Pointer path segment used as the map key is embedded directly into a SpEL expression without sanitization or validation. Affected versions: Spring Data REST 3.7.0 through 3.7.19; 4.3.0 through 4.3.16; 4.4.0 through 4.4.14; 4.5.0 through 4.5.11; 5.0.0 through 5.0.5.