CVE-2026-17863

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Inappropriate implementation in Browser in Google Chrome on Windows prior to 151.0.7922.72 allowed a local attacker to perform privilege escalation via a malicious file. (Chromium security severity: Medium)

CVSS v3
7.8
Vendor severity
MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 30, 2026

Last Modified

August 3, 2026

Advisory Details (2)

Auto-updated Jul 30, 2026
No patch confirmed yet.
generic

Chromium

https://issues.chromium.org/issues/520468718
generic

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-17863(1)

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 rangeFixed inDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 151.0.7922.47-1 (394 versions)151.0.7922.71-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb12u1 (160 versions)151.0.7922.71-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (162 versions)——

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 32× in last 7d / 158× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 170 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-17863?
CVE-2026-17863 is a high vulnerability published on July 30, 2026. Inappropriate implementation in Browser in Google Chrome on Windows prior to 151.0.7922.72 allowed a local attacker to perform privilege escalation via a malicious file. (Chromium security severity: Medium)
When was CVE-2026-17863 disclosed?
CVE-2026-17863 was first published in the National Vulnerability Database on July 30, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17863 actively exploited?
CVE-2026-17863 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.7% of all scored CVEs.
What is the CVSS score of CVE-2026-17863?
CVE-2026-17863 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-17863?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17863, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-17863

Explore →

Is Your Infrastructure Affected by CVE-2026-17863?

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

Start Free Scan →Browse All CVEs