ChromeWeb browser · Google
CVE-2026-14150
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 · uneditedInsufficient validation of untrusted input in Speech in Google Chrome prior to 150.0.7871.47 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Low)
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 · moderate confidenceInsufficient validation of untrusted input in Chrome's Speech component prior to version 150.0.7871.47 allows a remote attacker with a compromised renderer process to perform UI spoofing via a crafted HTML page. The vulnerability stems from missing input sanitization in speech-related functionality that can be exploited to manipulate the user interface.
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
< 150.0.7871.47CVSS 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
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N
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.
-
Determine installed Chrome versionOpen Chrome and navigate to chrome://version, or click Help > About Google Chrome. Note the version number displayed.Affected if The displayed version number is less than 150.0.7871.47 (e.g., 150.0.7871.0, 149.x.x.x, etc.)
-
Confirm Chrome is the affected browserVerify the browser is Google Chrome and not a Chromium-based alternative (such as Edge, Brave, or Vivaldi). Check the application name in the About dialog.Affected if The browser is Google Chrome and version is below 150.0.7871.47
-
Verify Speech component accessibilitySince this vulnerability targets Chrome's Speech component, confirm Chrome is in regular use with speech features potentially enabled (e.g., Chrome's built-in speech recognition APIs, voice input features, or extensions using speech functionality).Affected if Chrome is actively used and the version is vulnerable, regardless of whether speech features are actively employed at the moment of check
A user is affected if they are running Google Chrome version 150.0.7871.47 or any version prior to that on any platform where the browser is installed.
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 · scoped150.0.7871.47
Update Google Chrome to version 150.0.7871.47 or later to remediate this vulnerability. Organizations should ensure standard endpoint patch management processes include browser updates.
Chrome 150.0.7871.47 or later
- 1. Open Google Chrome on your system
- 2. Navigate to Chrome menu > Help > About Google Chrome
- 3. The browser will check for updates automatically
- 4. If version is below 150.0.7871.47, download and install the latest version from google.com/chrome
- 5. Restart the browser to complete the update
- 6. Verify the installed version is 150.0.7871.47 or higher 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
- Consultation1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14150 — 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-14150 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