Advisory record · GHSA-p6xc-xr62-6r2g

Apache Log4j2 vulnerable to Improper Input Validation and Uncontrolled Recursion

CVSS 8.6 HighCriticalEPSS 1.00 · 99th percentile

Critical, because:

  • CVSS score 8.6 (7.0 or more) and EPSS 1.00 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 18 Dec 2021, 18:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.logging.log4j:log4j-coreMaven>=2.4.0, <2.12.3 || >=2.13.0, <2.17.0 || <2.3.12.12.3, 2.17.0, 2.3.1
org.ops4j.pax.logging:pax-logging-log4j2Maven>=1.8.0, <1.9.2 || >=1.10.0, <1.10.9 || >=1.11.0, <1.11.12 || >=2.0.0, <2.0.131.9.2, 1.10.9, 1.11.12, 2.0.13
Identifiers
GHSA-p6xc-xr62-6r2g · CVE-2021-45105
Weakness (CWE)
CWE-20 · CWE-674
Published
18 Dec 2021
Updated
9 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Apache Log4j2 (log4j-core) versions 2.0-alpha1 through 2.16.0, excluding 2.12.3, are vulnerable, and pax-logging-log4j2 is also listed as affected in some older lines. An attacker who can control Thread Context Map data can cause a denial of service by supplying a crafted string that triggers uncontrolled recursion through self-referential lookups. Upgrade log4j-core to 2.17.0, 2.12.3, or 2.3.1 for the affected lines, and pax-logging-log4j2 to 1.9.2, 1.10.9, 1.11.12, or 2.0.13.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.6 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 1.00, the 99th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.