CVE-2026-87618

HIGHPre-NVD 8.38.3—
EchelonGraph scoreHIGH confidence

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

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

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

Incorrect reference resolution in Storage in Google Chrome on on Windows prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Low)

CVSS v3
8.3
Vendor severity
LOWper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Low)
EG Score
8.3(high)
EG Risk
37(Track)
EG Risk 37/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
Severity83% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

September 9, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Sep 9, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

Chromium

https://issues.chromium.org/issues/497203958
generic🔴 Active Exploitation

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0808145027.html

Vendor Advisories for CVE-2026-87618(1)

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

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 34× in last 7d / 54× 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.

  1. 2026-09-19 02:17 UTCEG score recompute
  2. 2026-09-19 02:17 UTCVendor advisory
  3. 2026-09-19 02:17 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-18 14:25 UTCVendor advisory
  6. 2026-09-18 14:25 UTCGHSA enrichment
  7. 2026-09-18 02:33 UTCEG score recompute
  8. 2026-09-18 02:33 UTCVendor advisory
  9. 2026-09-18 02:33 UTCGHSA enrichment
  10. 2026-09-17 19:32 UTCEPSS rescore
  11. 2026-09-17 14:41 UTCVendor advisory
  12. 2026-09-17 14:41 UTCGHSA enrichment
  13. 2026-09-17 02:49 UTCVendor advisory
  14. 2026-09-17 02:49 UTCGHSA enrichment
  15. 2026-09-16 14:52 UTCEG score recompute
  16. 2026-09-16 14:52 UTCVendor advisory
  17. 2026-09-16 14:52 UTCGHSA enrichment
  18. 2026-09-16 14:09 UTCEPSS rescore
  19. 2026-09-16 05:15 UTCEPSS rescore
  20. 2026-09-16 02:59 UTCVendor advisory
  21. 2026-09-16 02:59 UTCGHSA enrichment
  22. 2026-09-15 15:07 UTCVendor advisory
  23. 2026-09-15 15:07 UTCGHSA enrichment
  24. 2026-09-15 03:15 UTCEG score recompute
  25. 2026-09-15 03:15 UTCVendor advisory
Show 29 more
  1. 2026-09-15 03:15 UTCGHSA enrichment
  2. 2026-09-15 03:12 UTCEPSS rescore
  3. 2026-09-14 15:23 UTCGHSA enrichment
  4. 2026-09-14 03:29 UTCEG score recompute
  5. 2026-09-14 03:29 UTCGHSA enrichment
  6. 2026-09-13 15:37 UTCGHSA enrichment
  7. 2026-09-13 03:45 UTCGHSA enrichment
  8. 2026-09-12 15:54 UTCEG score recompute
  9. 2026-09-12 15:54 UTCGHSA enrichment
  10. 2026-09-12 04:02 UTCGHSA enrichment
  11. 2026-09-11 16:10 UTCEG score recompute
  12. 2026-09-11 16:10 UTCGHSA enrichment
  13. 2026-09-11 14:53 UTCEPSS rescore
  14. 2026-09-11 14:53 UTCEPSS rescore
  15. 2026-09-11 04:18 UTCGHSA enrichment
  16. 2026-09-10 16:26 UTCEG score recompute
  17. 2026-09-10 16:26 UTCGHSA enrichment
  18. 2026-09-10 04:34 UTCGHSA enrichment
  19. 2026-09-10 04:02 UTCGHSA enrichment
  20. 2026-09-09 17:48 UTCGHSA enrichment
  21. 2026-09-09 15:54 UTCEG score recompute
  22. 2026-09-09 15:54 UTCGHSA enrichment
  23. 2026-09-09 14:28 UTCGHSA enrichment
  24. 2026-09-09 13:55 UTCEG score recompute▲ 2.90
  25. 2026-09-09 13:55 UTCGHSA enrichment
  26. 2026-09-09 13:55 UTCMITRE cvelistV5CVSS v3 → 8.3 · severity → HIGH
  27. 2026-09-09 01:22 UTCNVD update
  28. 2026-09-09 00:59 UTCEG score recompute
  29. 2026-09-09 00:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-87618?
CVE-2026-87618 is a high vulnerability published on September 9, 2026. Incorrect reference resolution in Storage in Google Chrome on on Windows prior to 153.0.8010.36 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Low)
When was CVE-2026-87618 disclosed?
CVE-2026-87618 was first published in the National Vulnerability Database on September 9, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-87618 actively exploited?
CVE-2026-87618 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 74.5% of all scored CVEs.
What is the CVSS score of CVE-2026-87618?
CVE-2026-87618 has a CVSS v3.1 base score of 8.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-87618?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-87618, 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

Explore the affected products and dependency analysis for CVE-2026-87618

Explore →

Is Your Infrastructure Affected by CVE-2026-87618?

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

Start Free Scan →Browse All CVEs