CVE-2022-23307

CRITICALPre-NVD 8.89.8
EchelonGraph scoreMEDIUM confidence

“▲” beside the score: it is higher than the CVSS score beside it.

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-01-19. The CNA's CVSS baseline 8.8; sources differ by 1.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 4 sources updated this weekElevated

Also known asEUVD-2022-0575 (ENISA EUVD) · GHSA-f7vh-qwp3-x37m (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 54%
CISA-KEV: Not listedEPSS PROB: 54%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (Apache Software Foundation) states them in the record's workaround: "Upgrade to Apache Log4j 2 and Apache Chainsaw 2.1.0."

CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.

CVSS v3
8.8
EG Score
9.8CRITICALmedium confidence
EG Risk
66
EG Risk 66/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation54% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
54%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
54% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

January 18, 2022

Last Modified

May 27, 2026

Advisory Details (2)

Auto-updated May 22, 2026
Patch available.

Patch Availability(24)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhateap7-xml-security-0:2.2.3-2.redhat_00001.1.el7eap2024-11-25redhat
redhateap7-log4j-jboss-logmanager-0:1.2.2-1.Final_redhat_00002.1.ep7.el72024-08-26redhat
redhatjbossweb-0:7.5.32-2.Final_redhat_1.2.ep6.el62022-06-30redhat
redhatpatch2022-06-30redhat
redhatjbossweb-0:7.5.32-2.Final_redhat_1.2.ep6.el72022-06-30redhat
redhatorg.jboss.logmanager/log4j-jboss-logmanager:1.2.2.Final-redhat-000022022-04-11redhat
redhateap7-log4j-0:2.17.1-1.redhat_00001.1.el8eap2022-04-11redhat
redhateap7-log4j-0:2.17.1-1.redhat_00001.1.el7eap2022-04-11redhat
redhatlog4j2022-02-23redhat
redhattomcat-native-0:1.2.23-26.redhat_26.ep7.el72022-02-14redhat
redhatlog4j-eap62022-02-14redhat
redhatpatch2022-02-08redhat
redhatsnmp4j-0:3.6.4-0.1.el8ev2022-02-08redhat
redhatrh-sso7-keycloak-0:15.0.4-1.redhat_00003.1.el7sso2022-02-07redhat
redhatrh-sso-7/sso74-openshift-rhel8:7.4-452022-02-07redhat
redhatrh-sso7-keycloak-0:15.0.4-1.redhat_00003.1.el8sso2022-02-07redhat
redhatlog4j-0:1.2.17-18.el7_42022-02-07redhat
redhatrh-sso-7/sso7-rhel8-operator-bundle:7.5.1-92022-02-07redhat
redhatrh-sso-7/sso74-openj9-openshift-rhel8:7.4-602022-02-07redhat
redhatrh-maven36-log4j12-0:1.2.17-23.4.el72022-02-03redhat
redhateap7-log4j-jboss-logmanager-0:1.2.2-1.Final_redhat_00002.1.el7eap2022-02-03redhat
redhatlog4j-jboss-logmanager-0:1.1.4-3.Final_redhat_00002.1.ep6.el72022-02-03redhat
mavenlog4j:log4j—ghsa
mavenorg.zenframework.z8.dependencies.commons:log4j-1.2.17—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 6 ecosystems)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
log4j:log4j1.1.3 ... 1.2.9 (14 versions)
  • every version through 1.2.17: no fix on record
—
org.zenframework.z8.dependencies.commons:log4j-1.2.172.0
  • every version through 2.0: no fix on record
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j1.21.2.17-10
  • every version up to 1.2.17-10+deb11u1: fixed in 1.2.17-10+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j1.2—
  • every version up to 1.2.17-11: fixed in 1.2.17-11
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j1.2—
  • every version up to 1.2.17-11: fixed in 1.2.17-11
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j1.2—
  • every version up to 1.2.17-11: fixed in 1.2.17-11
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j1.21.2.17-7, 1.2.17-7+deb9u1
  • every version up to 1.2.17-7+deb9u2: fixed in 1.2.17-7+deb9u2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(15)

Data Freshness Timeline

(refreshed 24× in last 7d / 83× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 226 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:30 UTCEPSS rescoreEPSS 54% · 99th percentile
  2. 2026-11-01 14:13 UTCEG score recompute
  3. 2026-11-01 14:13 UTCVendor advisory
  4. 2026-11-01 14:13 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  5. 2026-10-31 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
  6. 2026-10-31 12:20 UTCEG score recompute
  7. 2026-10-31 12:20 UTCVendor advisory
  8. 2026-10-31 12:20 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  9. 2026-10-30 16:30 UTCEPSS rescoreEPSS 54% · 99th percentile
  10. 2026-10-30 10:26 UTCEG score recompute
  11. 2026-10-30 10:26 UTCVendor advisory
  12. 2026-10-30 10:26 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  13. 2026-10-29 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
  14. 2026-10-29 08:34 UTCEG score recompute
  15. 2026-10-29 08:34 UTCVendor advisory
  16. 2026-10-29 08:33 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  17. 2026-10-28 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
  18. 2026-10-28 06:36 UTCEG score recompute
  19. 2026-10-28 06:36 UTCVendor advisory
  20. 2026-10-28 06:35 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  21. 2026-10-27 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
  22. 2026-10-27 04:43 UTCEG score recompute
  23. 2026-10-27 04:43 UTCVendor advisory
  24. 2026-10-27 04:43 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  25. 2026-10-25 22:24 UTCVendor advisory
Show 74 more
  1. 2026-10-25 22:24 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  2. 2026-10-25 18:13 UTCEG score recompute
  3. 2026-10-25 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
  4. 2026-10-24 20:31 UTCEG score recompute
  5. 2026-10-24 20:31 UTCVendor advisory
  6. 2026-10-24 20:31 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  7. 2026-10-24 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
  8. 2026-10-23 18:39 UTCEG score recompute
  9. 2026-10-23 18:39 UTCVendor advisory
  10. 2026-10-23 18:38 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  11. 2026-10-22 16:45 UTCEG score recompute
  12. 2026-10-22 16:45 UTCVendor advisory
  13. 2026-10-22 16:45 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  14. 2026-10-22 16:30 UTCEPSS rescoreEPSS 54% · 99th percentile
  15. 2026-10-21 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
  16. 2026-10-21 14:50 UTCEG score recompute
  17. 2026-10-21 14:50 UTCVendor advisory
  18. 2026-10-21 14:50 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  19. 2026-10-20 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
  20. 2026-10-20 12:57 UTCEG score recompute
  21. 2026-10-20 12:57 UTCVendor advisory
  22. 2026-10-20 12:57 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  23. 2026-10-19 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
  24. 2026-10-19 11:02 UTCEG score recompute
  25. 2026-10-19 11:02 UTCVendor advisory
  26. 2026-10-19 11:02 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  27. 2026-10-18 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
  28. 2026-10-18 07:55 UTCEG score recompute
  29. 2026-10-18 07:55 UTCVendor advisory
  30. 2026-10-18 07:55 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  31. 2026-10-17 06:01 UTCEG score recompute
  32. 2026-10-17 06:01 UTCVendor advisory
  33. 2026-10-17 06:01 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  34. 2026-10-16 16:34 UTCEPSS rescoreEPSS 54% · 99th percentile
  35. 2026-10-16 04:07 UTCEG score recompute
  36. 2026-10-16 04:07 UTCVendor advisory
  37. 2026-10-16 04:06 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  38. 2026-10-15 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
  39. 2026-10-15 01:04 UTCEG score recompute
  40. 2026-10-15 01:04 UTCVendor advisory
  41. 2026-10-15 01:04 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  42. 2026-10-14 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
  43. 2026-10-13 22:15 UTCEG score recompute
  44. 2026-10-13 22:15 UTCVendor advisory
  45. 2026-10-13 22:15 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  46. 2026-10-13 16:29 UTCEPSS rescoreEPSS 54% · 98th percentile
  47. 2026-10-12 19:01 UTCVendor advisory
  48. 2026-10-12 19:01 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
  49. 2026-10-12 18:59 UTCEG score recompute
  50. 2026-10-11 23:25 UTCEG score recompute
  51. 2026-10-11 13:44 UTCEPSS rescoreEPSS 54% · 98th percentile
  52. 2026-10-10 19:56 UTCEPSS rescoreEPSS 54% · 98th percentile
  53. 2026-10-09 20:04 UTCEPSS rescoreEPSS 54% · 98th percentile
  54. 2026-10-08 16:40 UTCEPSS rescoreEPSS 54% · 98th percentile
  55. 2026-10-08 08:35 UTCOSV refresh
  56. 2026-10-07 23:45 UTCEPSS rescoreEPSS 54% · 98th percentile
  57. 2026-10-06 15:14 UTCEPSS rescoreEPSS 54% · 98th percentile
  58. 2026-10-03 14:22 UTCEPSS rescoreEPSS 54% · 98th percentile
  59. 2026-09-30 15:50 UTCEG score recompute
  60. 2026-09-30 15:00 UTCEPSS rescoreEPSS 54% · 98th percentile
  61. 2026-09-27 13:41 UTCEPSS rescoreEPSS 54% · 98th percentile
  62. 2026-09-24 14:00 UTCEPSS rescoreEPSS 54% · 98th percentile
  63. 2026-09-23 13:45 UTCEPSS rescoreEPSS 54% · 98th percentile
  64. 2026-09-18 14:20 UTCOSV refresh
  65. 2026-09-17 19:23 UTCEPSS rescoreEPSS 54% · 98th percentile
  66. 2026-09-16 14:05 UTCEPSS rescoreEPSS 54% · 98th percentile
  67. 2026-09-15 03:06 UTCEPSS rescoreEPSS 54% · 98th percentile
  68. 2026-09-12 14:57 UTCEPSS rescoreEPSS 54% · 98th percentile
  69. 2026-09-11 14:49 UTCEPSS rescoreEPSS 54% · 98th percentile
  70. 2026-09-11 09:33 UTCEPSS rescoreEPSS 54% · 98th percentile
  71. 2026-09-08 21:57 UTCEPSS rescoreEPSS 54% · 98th percentile
  72. 2026-09-06 13:45 UTCEPSS rescoreEPSS 54% · 98th percentile
  73. 2026-09-05 15:25 UTCEPSS rescoreEPSS 54% · 98th percentile
  74. 2026-09-04 13:57 UTCEPSS rescoreEPSS 54% · 98th percentile

Frequently asked(5)

What is CVE-2022-23307?
CVE-2022-23307 is a critical-severity vulnerability; its CVE record was published on January 18, 2022. CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.
When was the CVE record for CVE-2022-23307 published?
The CVE record for CVE-2022-23307 was published on January 18, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 27, 2026; the record at its source may have been updated since.
Is CVE-2022-23307 actively exploited?
CVE-2022-23307 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-23307?
CVE-2022-23307 has a CVSS base score of 8.8 (the CNA's own assessment, by apache; NVD's own analysis pending). EchelonGraph synthesises the CNA's CVSS + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2022-23307?
A fix for CVE-2022-23307 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (Apache Software Foundation) states them in the record's workaround: "Upgrade to Apache Log4j 2 and Apache Chainsaw 2.1.0." The vendor advisories EchelonGraph has for CVE-2022-23307 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-23307

Explore →

Is Your Infrastructure Affected by CVE-2022-23307?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.