HighGHSA-p6xc-xr62-6r2gCVE-2021-45105

Apache Log4j2 vulnerable to Improper Input Validation and Uncontrolled Recursion

Published 18 Dec 2021 · Updated 9 Jun 2026

Is your project on an affected org.apache.logging.log4j:log4j-core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=2.4.0 <2.12.3
Fixed in
2.12.3
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j-core -DdepVersion=2.12.3 -DforceVersion=true
Affected
>=2.13.0 <2.17.0
Fixed in
2.17.0
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j-core -DdepVersion=2.17.0 -DforceVersion=true
Affected
<2.3.1
Fixed in
2.3.1
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j-core -DdepVersion=2.3.1 -DforceVersion=true
Affected
>=1.8.0 <1.9.2
Fixed in
1.9.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.ops4j.pax.logging:pax-logging-log4j2 -DdepVersion=1.9.2 -DforceVersion=true
Affected
>=1.10.0 <1.10.9
Fixed in
1.10.9
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.ops4j.pax.logging:pax-logging-log4j2 -DdepVersion=1.10.9 -DforceVersion=true
Affected
>=1.11.0 <1.11.12
Fixed in
1.11.12
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.ops4j.pax.logging:pax-logging-log4j2 -DdepVersion=1.11.12 -DforceVersion=true
Affected
>=2.0.0 <2.0.13
Fixed in
2.0.13
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.ops4j.pax.logging:pax-logging-log4j2 -DdepVersion=2.0.13 -DforceVersion=true

Details

Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0 and 2.12.3.

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.

Is GHSA-p6xc-xr62-6r2g in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.logging.log4j:log4j-core, and gives you the command that fixes it.

More advisories for org.apache.logging.log4j:log4j-core

  • MediumCVE-2026-34479Apache Log4j 1 to Log4j 2 bridge: silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters · 10 Apr 2026
  • MediumCVE-2026-34480Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters · 10 Apr 2026
  • MediumCVE-2026-34478Apache Log4j Core: log injection in `Rfc5424Layout` due to silent configuration incompatibility · 10 Apr 2026
  • MediumCVE-2026-34477Apache Log4j Core: `verifyHostName` attribute silently ignored in TLS configuration · 10 Apr 2026
  • MediumCVE-2025-68161Apache Log4j does not verify the TLS hostname in its Socket Appender · 18 Dec 2025
  • HighCVE-2023-26464Apache Log4j 1.x (EOL) allows Denial of Service (DoS) · 10 Mar 2023
All 12 advisories for org.apache.logging.log4j:log4j-core

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.