Medium

Improper Input Validation and Injection in Apache Log4j2

  • Disclosed: 04.01.2022
  • Updated: 11.10.2026 12:22

Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to an attack where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code. 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.

Affected packages

Only the org.apache.logging.log4j:log4j-core package is directly affected by this vulnerability. The org.apache.logging.log4j:log4j-api should be kept at the same version as the org.apache.logging.log4j:log4j-core package to ensure compatability if in use.

This issue does not impact default configurations of Log4j2 and requires an attacker to have control over the Log4j2 configuration, which reduces the likelihood of being exploited.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Java / Kotlin (Maven) org.apache.logging.log4j:log4j-core >= 2.0-beta7, < 2.3.2, >= 2.4, < 2.12.4, >= 2.13.0, < 2.17.1 2.3.2, 2.12.4, 2.17.1
Java / Kotlin (Maven) org.ops4j.pax.logging:pax-logging-log4j2 >= 1.8.0, < 1.9.2, >= 1.10.0, < 1.10.9, >= 1.11.0, < 1.11.13, >= 2.0.0, < 2.0.14 1.9.2, 1.10.9, 1.11.13, 2.0.14

References

CVSS score 6.6/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-20, CWE-74
Platform
Java / Kotlin (Maven)
Package
org.apache.logging.log4j:log4j-core, org.ops4j.pax.logging:pax-logging-log4j2
Disclosed
04.01.2022
Updated
11.10.2026 12:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-8489-44mv-ggj8 - CC BY 4.0

Vulnerability history: org.apache.logging.log4j:log4j-core

All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (11) in the archive
Total entries
11
First → latest
01.2020 04.2026
Without a fix
0
Exploited in attacks
2

Severity breakdown

  • Critical 3
  • High 2
  • Medium 5
  • Low 1

Disclosures per year

  1. 2020: 2
  2. 2021: 3
  3. 2022: 1
  4. 2023: 1
  5. 2024: 0
  6. 2025: 1
  7. 2026: 3
Severity:
  1. High · 7.5 CVE-2023-26464 >= 1.0.4, < 2.0 2.0
  2. Improper Input Validation and Injection in Apache Log4j2 this entry
    Medium · 6.6 CVE-2021-44832 >= 2.0-beta7, < 2.3.2, >= 2.4, < 2.12.4, >= 2.13.0, < 2.17.1 2.3.2, 2.12.4, 2.17.1
  3. High · 8.6 CVE-2021-45105 >= 2.4.0, < 2.12.3, >= 2.13.0, < 2.17.0, < 2.3.1 2.12.3, 2.17.0, 2.3.1
  4. Critical · 9.0 Exploited in attacks CVE-2021-45046 >= 2.13.0, < 2.16.0, >= 2.4.0, < 2.12.2, < 2.3.1 2.16.0, 2.12.2, 2.3.1
  5. Critical · 10.0 Exploited in attacks CVE-2021-44228 >= 2.13.0, < 2.15.0, >= 2.0-beta9, < 2.3.1, >= 2.4, < 2.12.2 2.15.0, 2.3.1, 2.12.2
  6. Critical · 9.8 CVE-2017-5645 >= 2.0, < 2.8.2 2.8.2

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.