Integer overflow in V8 in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
CVE-2026-10963
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-05. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- 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.8(medium)
- EG Risk
- 40(Track)EG Risk 40/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 computedSeverity88% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
June 4, 2026
Last Modified
July 22, 2026
Advisory Details (2)
Auto-updated Jun 5, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.htmlVendor Advisories for CVE-2026-10963(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 113.0.5672.126-1 ... 148.0.7778.96-3 (363 versions) | 149.0.7827.53-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 149.0.7827.53-1~deb12u1 (129 versions) | 149.0.7827.53-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (130 versions) | 149.0.7827.53-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 128× 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 299 total refreshes for this CVE.
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 03:24 UTCEG score recompute
- 2026-08-25 03:24 UTCVendor advisory
- 2026-08-25 03:24 UTCGHSA enrichment
- 2026-08-23 23:57 UTCVendor advisory
- 2026-08-23 23:57 UTCGHSA enrichment
- 2026-08-23 12:39 UTCEG score recompute
- 2026-08-23 12:39 UTCVendor advisory
- 2026-08-23 12:39 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 20:09 UTCGHSA enrichment
- 2026-08-21 08:36 UTCEG score recompute
- 2026-08-21 08:36 UTCVendor advisory
- 2026-08-21 08:36 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 21:18 UTCVendor advisory
- 2026-08-20 21:18 UTCGHSA enrichment
- 2026-08-20 09:53 UTCEG score recompute
- 2026-08-20 09:53 UTCVendor advisory
- 2026-08-20 09:53 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 14:33 UTCEG score recompute
- 2026-08-17 14:33 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-17 14:33 UTCGHSA enrichment
- 2026-08-17 02:58 UTCEG score recompute
- 2026-08-17 02:58 UTCVendor advisory
- 2026-08-17 02:58 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:53 UTCEG score recompute
- 2026-08-16 14:53 UTCVendor advisory
- 2026-08-16 14:53 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-16 02:13 UTCVendor advisory
- 2026-08-16 02:13 UTCGHSA enrichment
- 2026-08-15 14:08 UTCEG score recompute
- 2026-08-15 14:08 UTCVendor advisory
- 2026-08-15 14:08 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 21:10 UTCVendor advisory
- 2026-08-14 21:10 UTCGHSA enrichment
- 2026-08-14 09:53 UTCGHSA enrichment
- 2026-08-13 22:36 UTCEG score recompute
- 2026-08-13 22:36 UTCVendor advisory
- 2026-08-13 22:36 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 09:07 UTCVendor advisory
- 2026-08-13 09:07 UTCGHSA enrichment
- 2026-08-12 21:46 UTCEG score recompute
- 2026-08-12 21:46 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 10:29 UTCVendor advisory
- 2026-08-12 10:29 UTCGHSA enrichment
- 2026-08-11 23:10 UTCEG score recompute
- 2026-08-11 23:10 UTCVendor advisory
- 2026-08-11 23:10 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 11:53 UTCVendor advisory
- 2026-08-11 11:53 UTCGHSA enrichment
- 2026-08-11 00:34 UTCEG score recompute
- 2026-08-11 00:34 UTCVendor advisory
- 2026-08-11 00:34 UTCGHSA enrichment
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 13:16 UTCGHSA enrichment
- 2026-08-10 01:59 UTCGHSA enrichment
- 2026-08-09 14:43 UTCEG score recompute
- 2026-08-09 14:43 UTCVendor advisory
- 2026-08-09 14:43 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 03:26 UTCEG score recompute
- 2026-08-09 03:26 UTCVendor advisory
- 2026-08-09 03:26 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 16:09 UTCVendor advisory
- 2026-08-08 16:09 UTCGHSA enrichment
- 2026-08-08 04:51 UTCGHSA enrichment
- 2026-08-07 17:34 UTCEG score recompute
- 2026-08-07 17:34 UTCGHSA enrichment
- 2026-08-07 06:17 UTCVendor advisory
- 2026-08-07 06:17 UTCGHSA enrichment
- 2026-08-06 19:00 UTCEG score recompute
- 2026-08-06 19:00 UTCVendor advisory
- 2026-08-06 19:00 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 07:43 UTCVendor advisory
- 2026-08-06 07:43 UTCGHSA enrichment
- 2026-08-05 20:27 UTCEG score recompute
- 2026-08-05 20:27 UTCVendor advisory
- 2026-08-05 20:26 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 18:54 UTCEG score recompute
- 2026-08-04 18:54 UTCVendor advisory
- 2026-08-04 18:54 UTCGHSA enrichment
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 02:56 UTCGHSA enrichment
- 2026-08-03 15:37 UTCVendor advisory
- 2026-08-03 15:37 UTCGHSA enrichment
- 2026-08-02 22:13 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-10963?
When was CVE-2026-10963 disclosed?
Is CVE-2026-10963 actively exploited?
What is the CVSS score of CVE-2026-10963?
How do I remediate CVE-2026-10963?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10963
Is Your Infrastructure Affected by CVE-2026-10963?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.