CVE-2026-79257

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.4%CVSS: 9.6Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Use after free in Views 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.4% × 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.4%
EPSS %ILE
27th
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.

Vendor Advisories for CVE-2026-79257(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
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
—
Debian:13(1)
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
—
Debian:14(1)
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
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 34× in last 7d / 328× 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 587 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 487 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-79257?
CVE-2026-79257 is a critical-severity vulnerability; its CVE record was published on August 25, 2026. Use after free in Views 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-79257 published?
The CVE record for CVE-2026-79257 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-79257 actively exploited?
CVE-2026-79257 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79257?
CVE-2026-79257 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-79257?
A fix for CVE-2026-79257 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-79257 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-79257

Explore →

Is Your Infrastructure Affected by CVE-2026-79257?

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