Advisory record · GHSA-vp98-w2p3-mv35

Apache Log4j 1.x (EOL) allows Denial of Service (DoS)

CVSS 7.5 HighEPSS 0.019 · 80th percentile

Published by the GitHub Advisory Database at 10 Mar 2023, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.apache.logging.log4j:log4j-coreMaven>=1.0.4, <2.02.0
log4j:log4jMaven>=1.0.4, <2.02.0
Identifiers
GHSA-vp98-w2p3-mv35 · CVE-2023-26464
Weakness (CWE)
CWE-400 · CWE-502
Published
10 Mar 2023
Updated
2 Sept 2025

Machine-written summary

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

Log4j 1.x versions from 1.0.4 before 2.0, in the log4j-core and log4j packages, are vulnerable when the Chainsaw or SocketAppender components run on a JRE older than 1.7. An attacker who can get a specially crafted, deeply nested hashmap or hashtable logged and deserialized can exhaust memory and cause a denial of service. The source gives no fixed 1.x version; it recommends moving to Log4j 2.x, and notes that the product is no longer supported by its maintainer.

Written 7 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
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.019, the 80th 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.