CVE-2026-79275

CRITICALPre-NVD 9.69.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-25. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
9.6EG
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: 0.5%CVSS: 9.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Use after free in ANGLE in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)

CVSS v3
9.6
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
9.6CRITICALmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity96% × 45%
The EG Score, 9.6 of 10.
Exploitation0.5% × 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
0.5%
EPSS %ILE
39th
KEV
Not listed

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.

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

August 25, 2026

Last Modified

August 31, 2026

Advisory Details (2)

Auto-updated Oct 7, 2026
Patch available.
Web page

Chromium

https://issues.chromium.org/issues/536659904
Web page

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html

Vendor Advisories for CVE-2026-79275(4)

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.54.0-1.el8_102026-09-30redhat
redhatwebkit2gtk3-0:2.54.0-1.el9_82026-09-21redhat

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 3 ecosystems)
Debian:12(3)
PackageVulnerable rangeFix by version rangeDependents
chromium113.0.5672.126-1 ... 152.0.7977.64-1 (412 versions)
  • every version up to 152.0.7977.75-1~deb12u1: fixed in 152.0.7977.75-1~deb12u1
—
webkit2gtk2.40.1-1 ... 2.54.0-1~exp1 (168 versions)
  • every version on: no fix on record
—
wpewebkit2.38.6-1 ... 2.54.0-2 (56 versions)
  • every version on: no fix on record
—
Debian:13(3)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 152.0.7977.75-1~deb12u1 (178 versions)
  • every version up to 152.0.7977.75-1~deb13u1: fixed in 152.0.7977.75-1~deb13u1
—
webkit2gtk2.48.3-1 ... 2.53.92-1 (59 versions)
  • every version up to 2.54.0-1~deb13u1: fixed in 2.54.0-1~deb13u1
—
wpewebkit2.48.3-1 ... 2.54.0-2 (22 versions)
  • every version on: no fix on record
—
Debian:14(3)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (176 versions)
  • every version up to 152.0.7977.64-1: fixed in 152.0.7977.64-1
—
webkit2gtk2.48.3-1 ... 2.54.0-1~exp1 (61 versions)
  • every version on: no fix on record
—
wpewebkit2.48.3-1 ... 2.52.6-1 (20 versions)
  • every version up to 2.54.0-1: fixed in 2.54.0-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 34× in last 7d / 317× 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 100 of 571 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. None are among the latest 100 rows. The 471 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-79275?
CVE-2026-79275 is a critical-severity vulnerability; its CVE record was published on August 25, 2026. Use after free in ANGLE in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
When was the CVE record for CVE-2026-79275 published?
The CVE record for CVE-2026-79275 was published on August 25, 2026. 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 August 31, 2026; the record at its source may have been updated since.
Is CVE-2026-79275 actively exploited?
CVE-2026-79275 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79275?
CVE-2026-79275 has a CVSS v3.1 base score of 9.6 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-79275?
A fix for CVE-2026-79275 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-79275 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-2026-79275

Explore →

Is Your Infrastructure Affected by CVE-2026-79275?

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

Book a Demo →Browse All CVEs