CVE-2021-44832: Remote Code Execution via JDBC Appender in Apache Log4j2
- Vendors
- Cisco SystemsOracle CorporationDebian ProjectFedora ProjectApache Software Foundation
CVE-2021-44832 is a configuration-dependent remote code execution vulnerability in Apache Log4j2's JDBC Appender. It affects versions 2.0-beta7 through 2.17.0, excluding fixed releases 2.3.2 and 2.12.4. An attacker with permission to modify the logging configuration can configure a JDBC Appender whose data source references a JNDI LDAP URI pointing to an attacker-controlled server. Insufficient restriction of JNDI data source protocols can then permit execution of attacker-controlled code. Unlike the original Log4Shell vulnerability, exploitation requires control over logging configuration rather than merely attacker-controlled logged messages.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation permits arbitrary code execution in the affected application's execution context, potentially compromising confidentiality, integrity, and availability. The resulting access is bounded by the application's permissions; administrative or system-level privileges are not inherently granted by this vulnerability.
Mitigation
If you can’t patch tonight, do this now.
Restrict logging-configuration modification to trusted administrators and prevent unauthorized creation or replacement of configuration files in application directories. Where feasible, disable the JDBC Appender or remove configurations using remote JNDI data sources. Restrict outbound LDAP connectivity to reduce access to attacker-controlled servers. Message-lookup disabling options intended for other Log4j vulnerabilities do not address this configuration-based attack path.
Remediation
Patch, then assume compromise.
Upgrade Log4j Core to 2.17.1 for Java 8 or later, 2.12.4 for Java 7, or 2.3.2 for Java 6, or an appropriate later fixed release. These fixes restrict JNDI data source names to the java protocol. Update bundled copies through the affected application's vendor-supported patches. If Log4j API is used, keep it aligned with the Log4j Core version for compatibility.
Exploits
2 exploits validated by Mallory's analysis. Hidden: 4 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2021-44832 exploited in the wild?
- Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2021-44832?
- Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2021-44832, the earliest disclosed Apr 28, 2026.
- Is there a patch for CVE-2021-44832?
- Upgrade Log4j Core to 2.17.1 for Java 8 or later, 2.12.4 for Java 7, or 2.3.2 for Java 6, or an appropriate later fixed release. These fixes restrict JNDI data source names to the java protocol.
- What products are affected by CVE-2021-44832?
- Apache Software Foundation Log4j, Cisco Systems Cloudcenter, Oracle Corporation Communications Brm - Elastic Charging Engine, Oracle Corporation Communications Diameter Signaling Router, Oracle Corporation Communications Interactive Session Recorder, and at least 17 more.
- How severe is CVE-2021-44832?
- CVE-2021-44832 has a CVSS v3.1 score of 6.6 (Medium) and an EPSS score of 97.9% (100th percentile) as of Nov 4, 2026.
Recent activity
54 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.