CVE-2023-25363

CRITICALNVD 8.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2023-03-02. NVD baseline CVSS 8.8; sources differ by 1.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2023-29321 (ENISA EUVD) · GHSA-m6fv-rjwf-hmj9 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A use-after-free vulnerability in WebCore::RenderLayer::updateDescendantDependentFlags in WebKitGTK before 2.36.8 allows attackers to execute code remotely.

CVSS v3
8.8
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/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.
Exploitation1.0% × 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
1.0%
EPSS %ILE
62nd
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
1.0% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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

March 2, 2023

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Aug 28, 2026
Patch available.
Web page

WebKitGTK+: Multiple Vulnerabilities (GLSA 202305-32) — Gentoo security

https://security.gentoo.org/glsa/202305-32
Web page

242684 – (CVE-2023-25363) a heap-use-after-free in WebCore::RenderLayer::updateDescendantDependentFlags()

https://bugs.webkit.org/show_bug.cgi?id=242684
Web page

oss-security - WebKitGTK and WPE WebKit Security Advisory WSA-2023-0003

http://www.openwall.com/lists/oss-security/2023/04/21/3

Vendor Advisories for CVE-2023-25363(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatwebkit2gtk3-0:2.38.5-1.el82023-05-16redhat
redhatwebkit2gtk3-0:2.38.5-1.el92023-05-09redhat

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

(9 across 5 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
webkit2gtk2.32.3-1 ... 2.38.0-1~deb10u1 (54 versions)
  • every version up to 2.38.0-1~deb11u1: fixed in 2.38.0-1~deb11u1
—
wpewebkit2.32.3-2 ... 2.36.7-1~deb11u1 (25 versions)
  • every version up to 2.38.0-1~deb11u1: fixed in 2.38.0-1~deb11u1
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
webkit2gtk—
  • every version up to 2.38.0-1: fixed in 2.38.0-1
—
wpewebkit—
  • every version up to 2.38.0-1: fixed in 2.38.0-1
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
webkit2gtk—
  • every version up to 2.38.0-1: fixed in 2.38.0-1
—
wpewebkit—
  • every version up to 2.38.0-1: fixed in 2.38.0-1
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
webkit2gtk—
  • every version up to 2.38.0-1: fixed in 2.38.0-1
—
wpewebkit—
  • every version up to 2.38.0-1: fixed in 2.38.0-1
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
webkit2gtk2.24.2-1 ... 2.37.91-1 (139 versions)
  • every version up to 2.38.0-1~deb10u1: fixed in 2.38.0-1~deb10u1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 93× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 328 rows 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. None are among the latest 100 rows. The 228 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2023-25363?
CVE-2023-25363 is a critical-severity vulnerability; its CVE record was published on March 2, 2023. A use-after-free vulnerability in WebCore::RenderLayer::updateDescendantDependentFlags in WebKitGTK before 2.36.8 allows attackers to execute code remotely.
When was the CVE record for CVE-2023-25363 published?
The CVE record for CVE-2023-25363 was published on March 2, 2023. 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 November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-25363 actively exploited?
CVE-2023-25363 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (62nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-25363?
CVE-2023-25363 has a CVSS v3 base score of 8.8 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2023-25363?
A fix for CVE-2023-25363 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-25363 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-2023-25363

Explore →

Is Your Infrastructure Affected by CVE-2023-25363?

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