Advisory record · GHSA-8489-44mv-ggj8

Improper Input Validation and Injection in Apache Log4j2

CVSS 6.6 MediumEPSS 0.98 · 99th percentile

Published by the GitHub Advisory Database at 4 Jan 2022, 16:14 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.0-beta7, <2.3.2 || >=2.4, <2.12.4 || >=2.13.0, <2.17.12.3.2, 2.12.4, 2.17.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.13 || >=2.0.0, <2.0.141.9.2, 1.10.9, 1.11.13, 2.0.14
Identifiers
GHSA-8489-44mv-ggj8 · CVE-2021-44832
Weakness (CWE)
CWE-20 · CWE-74
Published
4 Jan 2022
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 from 2.0-beta7 through 2.17.0, excluding 2.3.2 and 2.12.4, are vulnerable, as are pax-logging-log4j2 versions from 1.8.0 through 2.0.13. An attacker who can modify the logging configuration file could add a JDBC Appender whose data source uses a JNDI URI, potentially executing remote code. Upgrade log4j-core to 2.17.1, 2.12.4, or 2.3.2, and pax-logging-log4j2 to 1.9.2, 1.10.9, 1.11.13, or 2.0.14 as appropriate.

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
6.6 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.98, 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.