ChromeWeb browser · Google
CVE-2026-3916
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOut 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)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn out-of-bounds read vulnerability exists in the Web Speech API component of Google Chrome versions prior to 146.0.7680.71. This memory corruption issue allows a remote attacker to read memory outside the intended buffer boundaries through a maliciously crafted HTML page, potentially enabling further exploitation for sandbox escape.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 146.0.7680.71CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionNavigate to chrome://version in the browser address bar, or run 'google-chrome --version' (or 'chromium --version') from the command lineAffected if The displayed version number is less than 146.0.7680.71
-
Verify Web Speech API availabilityOpen Chrome DevTools (F12), go to the Console tab, and type 'window.SpeechRecognition || window.webkitSpeechRecognition' to check if the API is exposedAffected if The command returns a function object rather than 'undefined', indicating the Web Speech API is enabled
-
Confirm browser can process HTML contentConfirm the browser is used for general web browsing and can load untrusted HTML pages from websites or local filesAffected if The browser regularly loads web content without additional sandboxing or restricted modes (such as Enterprise kiosk mode)
You are affected if your Chrome version is earlier than 146.0.7680.71 and the Web Speech API is accessible in your browser context.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped146.0.7680.71
Update Google Chrome to version 146.0.7680.71 or later to remediate this vulnerability. Organizations should prioritize patching given the CVSS 9.6 severity and sandbox escape potential.
Chrome 146.0.7680.71
- Open Google Chrome and navigate to Help > About Google Chrome to verify the current version
- If the version is below 146.0.7680.71, Chrome will automatically check for updates; click 'Update Google Chrome' if prompted
- Restart Chrome to complete the update
- Verify the installed version is 146.0.7680.71 or later via Help > About Google Chrome
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3916 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3916 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data