CVE-2026-87599

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

Improper input validation in Interstitials in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to spoof UI elements via a crafted HTML page. (Chromium security severity: Medium)

CVSS v3
5.4
Vendor severity
MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
EG Score
5.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/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)
Severity54% × 45%
The EG Score, 5.4 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
13th
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

September 9, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Sep 9, 2026
Patch available.
Web page

Chromium

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

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-87599(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 ... 153.0.8010.47-2~deb13u1 (422 versions)
  • every version up to 153.0.8010.52-1~deb12u1: fixed in 153.0.8010.52-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 153.0.8010.47-2~deb12u1 (185 versions)
  • every version up to 153.0.8010.47-2~deb13u1: fixed in 153.0.8010.47-2~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 152.0.7977.82-1~deb13u1 (183 versions)
  • every version up to 153.0.8010.47-1: fixed in 153.0.8010.47-1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-87599?
CVE-2026-87599 is a medium-severity vulnerability; its CVE record was published on September 9, 2026. Improper input validation in Interstitials in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to spoof UI elements via a crafted HTML page. (Chromium security severity: Medium)
When was the CVE record for CVE-2026-87599 published?
The CVE record for CVE-2026-87599 was published on September 9, 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 September 10, 2026; the record at its source may have been updated since.
Is CVE-2026-87599 actively exploited?
CVE-2026-87599 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-87599?
CVE-2026-87599 has a CVSS v3.1 base score of 5.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-87599?
A fix for CVE-2026-87599 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-87599 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-87599

Explore →

Is Your Infrastructure Affected by CVE-2026-87599?

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

Book a Demo →Browse All CVEs