CVE-2026-17776

MEDIUMPre-NVD 5.85.8
EchelonGraph scoreMEDIUM confidence

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

Score 5.8 from GitHub Security Advisory published 2026-07-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
5.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Policy bypass in Receiver in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)

CVSS v3
5.8
Vendor severity
MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
EG Score
5.8MEDIUMmedium confidence
EG Risk
26
EG Risk 26/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)
Severity58% × 45%
The EG Score, 5.8 of 10.
Exploitation0.2% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.2%
EPSS %ILE
8th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

July 30, 2026

Last Modified

August 4, 2026

Advisory Details (2)

Auto-updated Jul 31, 2026
Patch available.
Web page

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html

Vendor Advisories for CVE-2026-17776(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
chromium113.0.5672.126-1 ... 151.0.7922.47-1 (394 versions)
  • every version up to 151.0.7922.71-1~deb12u1: fixed in 151.0.7922.71-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb12u1 (160 versions)
  • every version up to 151.0.7922.71-1~deb13u1: fixed in 151.0.7922.71-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (161 versions)
  • every version up to 151.0.7922.71-1: fixed in 151.0.7922.71-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17776?
CVE-2026-17776 is a medium-severity vulnerability; its CVE record was published on July 30, 2026. Policy bypass in Receiver in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)
When was the CVE record for CVE-2026-17776 published?
The CVE record for CVE-2026-17776 was published on July 30, 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 4, 2026; the record at its source may have been updated since.
Is CVE-2026-17776 actively exploited?
CVE-2026-17776 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17776?
CVE-2026-17776 has a CVSS v3.1 base score of 5.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-17776?
A fix for CVE-2026-17776 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17776 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-17776

Explore →

Is Your Infrastructure Affected by CVE-2026-17776?

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

Book a Demo →Browse All CVEs