CVE-2026-17767

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory published 2026-07-30. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.3; 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
4.3EG
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.3%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Insufficient validation of untrusted input in WebView in Google Chrome on Android prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)

CVSS v3
4.3
Vendor severity
MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/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)
Severity43% × 45%
The EG Score, 4.3 of 10.
Exploitation0.3% × 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.3%
EPSS %ILE
16th
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 30, 2026
Patch available.
Web page

Chromium

https://issues.chromium.org/issues/511822402
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-17767(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(2)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17767?
CVE-2026-17767 is a medium-severity vulnerability; its CVE record was published on July 30, 2026. Insufficient validation of untrusted input in WebView in Google Chrome on Android prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
When was the CVE record for CVE-2026-17767 published?
The CVE record for CVE-2026-17767 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-17767 actively exploited?
CVE-2026-17767 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17767?
CVE-2026-17767 has a CVSS v3.1 base score of 4.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-17767?
A fix for CVE-2026-17767 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-17767 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-17767

Explore →

Is Your Infrastructure Affected by CVE-2026-17767?

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

Book a Demo →Browse All CVEs