Advisory record · GHSA-7rjr-3q55-vv33

Incomplete fix for Apache Log4j vulnerability

CVSS 9.0 CriticalCriticalIn CISA KEV · ransomwareEPSS 1.00 · 99th percentile

Critical, because:

  • In CISA’s KEV catalogue since 1 May 2023: it is known to be exploited.
  • CVSS score 9.0: 9.0 or more.
  • CVSS score 9.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 14 Dec 2021, 18:01 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.16.0 || >=2.4.0, <2.12.2 || <2.3.12.16.0, 2.12.2, 2.3.1
org.ops4j.pax.logging:pax-logging-log4j2Maven>=1.8.0, <1.9.2 || >=1.10.0, <1.10.8 || >=1.11.0, <1.11.11 || >=2.0.0, <2.0.121.9.2, 1.10.8, 1.11.11, 2.0.12
Identifiers
GHSA-7rjr-3q55-vv33 · CVE-2021-45046
Weakness (CWE)
CWE-502 · CWE-917
Published
14 Dec 2021
Updated
2 Oct 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
9.0 Critical 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Listed since 1 May 2023: known to be exploited. CISA reports use in ransomware campaigns.
  • EPSS 1.00, the 99th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

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