CVE-2026-15903

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Out of bounds read and write in V8 in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

CVSS v3
8.8
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation0.4% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.4%
EPSS %ILE
33rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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 20, 2026

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jul 22, 2026
Patch available.

Vendor Advisories for CVE-2026-15903(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 ... 150.0.7871.46-1~deb13u1 (390 versions)
  • every version up to 150.0.7871.181-1~deb12u1: fixed in 150.0.7871.181-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (156 versions)
  • every version up to 150.0.7871.181-1~deb13u1: fixed in 150.0.7871.181-1~deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
chromium138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (157 versions)
  • every version up to 150.0.7871.181-1: fixed in 150.0.7871.181-1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 54× 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 1,301 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 1,201 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-15903?
CVE-2026-15903 is a high-severity vulnerability; its CVE record was published on July 20, 2026. Out of bounds read and write in V8 in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
When was the CVE record for CVE-2026-15903 published?
The CVE record for CVE-2026-15903 was published on July 20, 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-15903 actively exploited?
CVE-2026-15903 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15903?
CVE-2026-15903 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-15903?
A fix for CVE-2026-15903 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-15903 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-15903

Explore →

Is Your Infrastructure Affected by CVE-2026-15903?

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