Skip to main content
MEDIUM

CVE-2021-44832

CVSS v3

6.6

MEDIUM

EPSS Score

97.9 %

exploit probability, as of 2026-10-19

CISA KEV

No

known exploited

Exploitation

—

SSVC status

Get an alert for each new CVE published for log4j-core.

Set up CVE WatchFree account · no credit card

Affected and fixed versions

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • org.apache.logging.log4j:log4j-coreMavenfrom 2.13.0 · fixed in 2.17.1
  • org.ops4j.pax.logging:pax-logging-log4j2Mavenfrom 2.0.0 · fixed in 2.0.14

Vendor advisories

  • CVE-2021-44832 Red Hat Product Security32 products fixed · 1 known affected

    log4j-core: remote code execution via JDBC Appender

    log4j-core as a component of Red Hat Integration Camel Quarkus 1

  • RHSA-2022:1299 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.4 security update

  • RHSA-2022:1297 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.4 security update

  • RHSA-2022:1296 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.4 security update

  • RHSA-2022:0485 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.8.31 security update

  • RHSA-2022:0493 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: OpenShift Container Platform 4.7.43 security update

15 more advisories

Full record on NVD

Description

Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.

Technical details

Published
2021-12-28

Frequently asked questions

What is CVE-2021-44832?

Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2.

Is CVE-2021-44832 actively exploited?

Active exploitation of CVE-2021-44832 has not been confirmed. Its EPSS score was 97.9% on 2026-10-19, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2021-44832?

CVE-2021-44832 has a CVSS v3 base score of 6.6 (MEDIUM severity).

Running log4j-core? Hear about its next vulnerability

CVE Watch matches each new CVE to the vendors and products you list (vendor and product, not the version) and puts it in your alerts with its KEV and EPSS status.

Get alerts for this productCISA KEV additions, October 2026Search CVEs

Already have an account? Open CVE WatchNo credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database