Out of bounds read in Web Speech in Google Chrome prior to 146.0.7680.71 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
CVE-2026-3916
Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-03-12. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.6; 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
- 9.6
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 9.6(medium)
- EG Risk
- 43(Track)EG Risk 43/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 computedSeverity96% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
March 11, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Sep 14, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_10.htmlVendor Advisories for CVE-2026-3916(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)
| 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 ... 145.0.7632.75-1~deb13u1 (321 versions) | 146.0.7680.71-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 146.0.7680.71-1~deb12u1 (87 versions) | 146.0.7680.71-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 146.0.7680.71-1~deb13u1 (88 versions) | 146.0.7680.71-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 27× 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 124 total refreshes for this CVE.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 19:40 UTCOSV refresh
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 11:50 UTCEG score recompute
- 2026-08-16 11:50 UTCVendor advisory
- 2026-08-16 11:50 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-15 00:51 UTCVendor advisory
- 2026-08-15 00:51 UTCGHSA enrichment
- 2026-08-14 20:37 UTCVendor advisory
- 2026-08-14 20:37 UTCGHSA enrichment
- 2026-08-14 16:17 UTCVendor advisory
- 2026-08-14 16:17 UTCGHSA enrichment
- 2026-08-14 12:02 UTCVendor advisory
- 2026-08-14 12:02 UTCGHSA enrichment
- 2026-08-14 07:47 UTCEG score recompute
- 2026-08-14 07:47 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 03:08 UTCGHSA enrichment
- 2026-08-12 22:54 UTCEG score recompute
- 2026-08-12 22:54 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-12 02:00 UTCVendor advisory
- 2026-08-12 02:00 UTCGHSA enrichment
- 2026-08-11 21:45 UTCEG score recompute
- 2026-08-11 21:45 UTCVendor advisory
- 2026-08-11 21:45 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 09:13 UTCVendor advisory
- 2026-08-11 09:13 UTCGHSA enrichment
- 2026-08-11 04:56 UTCEG score recompute
- 2026-08-11 04:56 UTCVendor advisory
- 2026-08-11 04:56 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 12:55 UTCVendor advisory
- 2026-08-10 12:55 UTCGHSA enrichment
- 2026-08-10 06:40 UTCVendor advisory
- 2026-08-10 06:40 UTCGHSA enrichment
- 2026-08-10 02:14 UTCVendor advisory
- 2026-08-10 02:14 UTCGHSA enrichment
- 2026-08-09 21:58 UTCGHSA enrichment
- 2026-08-09 17:43 UTCEG score recompute
- 2026-08-09 17:43 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 13:28 UTCVendor advisory
- 2026-08-09 13:28 UTCGHSA enrichment
- 2026-08-09 07:28 UTCEG score recompute
- 2026-08-09 07:28 UTCVendor advisory
- 2026-08-09 07:28 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 11:28 UTCVendor advisory
- 2026-08-08 11:28 UTCGHSA enrichment
- 2026-08-08 06:58 UTCVendor advisory
- 2026-08-08 06:58 UTCGHSA enrichment
- 2026-08-08 02:43 UTCGHSA enrichment
- 2026-08-07 22:28 UTCVendor advisory
- 2026-08-07 22:28 UTCGHSA enrichment
- 2026-08-07 18:13 UTCEG score recompute
- 2026-08-07 18:13 UTCGHSA enrichment
- 2026-08-06 19:52 UTCEG score recompute
- 2026-08-06 19:52 UTCVendor advisory
- 2026-08-06 19:52 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 10:31 UTCVendor advisory
- 2026-08-06 10:31 UTCGHSA enrichment
- 2026-08-06 06:15 UTCVendor advisory
- 2026-08-06 06:15 UTCGHSA enrichment
- 2026-08-06 02:00 UTCEG score recompute
- 2026-08-06 02:00 UTCVendor advisory
- 2026-08-06 02:00 UTCGHSA enrichment
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-125
- CVE-2013-0767EG 10.0EPSS p93HIGH
- CVE-2009-2523EG 10.0EPSS p98HIGH
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS p96CRITICAL
- CVE-2014-1522EG 9.3EPSS p92HIGH
- CVE-2013-0779EG 9.3EPSS p92HIGH
- CVE-2013-0778EG 9.3EPSS p90HIGH
- CVE-2012-3995EG 9.3EPSS p92HIGH
Frequently asked(5)
What is CVE-2026-3916?
When was CVE-2026-3916 disclosed?
Is CVE-2026-3916 actively exploited?
What is the CVSS score of CVE-2026-3916?
How do I remediate CVE-2026-3916?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-3916
Is Your Infrastructure Affected by CVE-2026-3916?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.