Advisory record · GHSA-jfh8-c2jp-5v3q

Remote code injection in Log4j

CVSS 10.0 CriticalCriticalIn CISA KEV · ransomwareEPSS 1.00 · 100th percentile

Critical, because:

  • In CISA’s KEV catalogue since 10 Dec 2021: it is known to be exploited.
  • CVSS score 10.0: 9.0 or more.
  • CVSS score 10.0 (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 10 Dec 2021, 00:40 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.13.0, <2.15.0 || >=2.0-beta9, <2.3.1 || >=2.4, <2.12.22.15.0, 2.3.1, 2.12.2
com.guicedee.services:log4j-coreMaven<=1.2.1.2-jre17No fixed version yet
org.xbib.elasticsearch:log4jMaven=6.3.2.1No fixed version yet
uk.co.nichesolutions.logging.log4j:log4j-coreMaven=2.6.3-CUSTOMNo fixed version yet
org.ops4j.pax.logging:pax-logging-log4j2Maven>=1.8.0, <1.9.2 || >=1.10.0, <1.10.8 || >=1.11.0, <1.11.10 || >=2.0.0, <2.0.111.9.2, 1.10.8, 1.11.10, 2.0.11
Identifiers
GHSA-jfh8-c2jp-5v3q · CVE-2021-44228
Weakness (CWE)
CWE-20 · CWE-400 · CWE-502 · CWE-917
Published
10 Dec 2021
Updated
22 Oct 2025

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
10.0 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:H GitHub Advisory Database
  • CISA KEV Listed since 10 Dec 2021: known to be exploited. CISA reports use in ransomware campaigns.
  • EPSS 1.00, the 100th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:10 UTC First seen by agentprime
  2. 31 Oct 2026, 15:10 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.