Skip to main content
No exploitation reportedFix available

CVE-2023-26464

No exploitation reported by the sources we read.

  • Published2023-03-10
  • Fixed in2.0
  • WeaknessCWE-502

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

** UNSUPPORTED WHEN ASSIGNED ** When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted (ie, deeply nested) hashmap or hashtable (depending on which logging component is in use) to be processed could exhaust the available memory in the virtual machine and achieve Denial of Service when the object is deserialized. This issue affects Apache Log4j before 2. Affected users are recommended to update to Log4j 2.x. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Timeline

dates in UTC
  1. 2023-03-1014:15CVE publishedNVD

Versions per branch

NVD · CISA-ADP · OSV
Apache Log4j
BranchAffectedFixed in
2.0≥ 1.0.4, < 2.02.0

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache Log4jother versions: unknown
    Affected
    • ≥ 1.0.4, < 2fixed in 2maven

    Not affected ≥ 2

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2023-05-05

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • apache-druidMinimOSall versions · no fixed version listedand 1 other package
  • apache-log4j1.2Ubuntu:Pro:16.04:LTSall versions · no fixed version listed
  • apache-log4j1.2Ubuntu:Pro:14.04:LTSall versions · no fixed version listed
  • apache-log4j1.2Ubuntu:20.04:LTSall versions · no fixed version listed
  • apache-log4j1.2Ubuntu:18.04:LTSall versions · no fixed version listed
  • druidWolfiall versions · no fixed version listed
  • druidChainguardall versions · no fixed version listedand 3 other packages
  • eap7-activemq-artemisRed Hat:jboss_enterprise_application_platform:7.4::el9all versions · fixed in 0:2.16.0-15.redhat_00049.1.el9eapand 15 other packages

73 more package ranges on OSV.dev

Vendor advisories

  • CVE-2023-26464 Red Hat Product Security441 products fixed · 26 known affected

    log4j1-socketappender: DoS via hashmap logging

    log4j.src as a component of Migration Toolkit for Applications 6 · log4j.src as a component of Migration Toolkit for Runtimes · jenkins.src as a component of OpenShift Developer Tools and Services · +23 more

  • RHSA-2024:10207 Red Hat Product Security59 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.3.11 Security update

  • RHSA-2024:10208 Red Hat Product Security26 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.1.8 on RHEL 7 security update

  • RHSA-2023:5485 Red Hat Product Security119 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.13 security update on RHEL 8

  • RHSA-2023:5486 Red Hat Product Security116 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.13 security update on RHEL 9

  • RHSA-2023:5484 Red Hat Product Security118 products fixed

    Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.13 security update on RHEL 7

2 more advisories

Full record on NVD

Fix

  1. Update Apache Log4j to 2.0
  2. Vendor fix Red Hat Product Security RHSA-2024:10207 · 59 productsBefore applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access…
  3. Vendor fix Red Hat Product Security RHSA-2023:5485 · 119 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  4. Vendor fix Red Hat Product Security RHSA-2023:5488 · 1 productBefore applying the update, back up your existing installation, including all applications, configuration files, databases and database settings, and so on. The References section of this erratum contains a download link (you must log in to download the update).
  5. Vendor fix Red Hat Product Security RHSA-2023:3663 · 2 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  6. Workaround from the vendor Red Hat Product Security RHSA-2024:10207 · 59 productsMitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
  7. No fix planned, says the vendor Red Hat Product Security CVE-2023-26464 · 4 productsOut of support scope

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2024-10-23
  • CISA-ADPCVSS 3.17.52024-10-23
  • NVDCVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-502known since 2026-10-23
  • NVDweakness (CWE)CWE-502read 2026-10-23
  • FIRST EPSSEPSS score1.9 %2026-11-08
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryHIGH2023-03-10

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2023-03-10
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-vp98-w2p3-mv35

Frequently asked questions

What is CVE-2023-26464?

** UNSUPPORTED WHEN ASSIGNED ** When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted (ie, deeply nested) hashmap or hashtable (depending on which logging component is in use) to be processed could exhaust the available memory in the virtual machine and achieve Denial of Service when the object is deserialized. This issue affects Apache Log4j before 2. Affected users are recommended to update to Log4j 2.x. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Is CVE-2023-26464 actively exploited?

Active exploitation of CVE-2023-26464 has not been confirmed. Its EPSS score was 1.9% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-26464?

CVE-2023-26464 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running Apache Log4j? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record