dbcve.org
ChromeWeb browser · Google

CVE-2026-7960

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 148.0.7778.96 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Race in Speech in Google Chrome prior to 148.0.7778.96 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)

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 confidence

A race condition in Chrome's Speech component prior to version 148.0.7778.96 allows a remote attacker with already-compromised renderer process access to leak potentially sensitive information from process memory via a specially crafted HTML page.

MitigationUpdate Google Chrome to version 148.0.7778.96 or later. Until updated, restrict or disable Chrome usage in environments where the renderer process could be compromised.

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
Affected:< 148.0.7778.96

CVSS 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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on this page.
    Affected if The displayed version number is less than 148.0.7778.96 (for example, 148.0.7778.0, 147.x.x.x, etc.)
  2. Verify Chrome version via command line
    On Windows, run 'chrome --version' in Command Prompt or PowerShell. On macOS, run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in Terminal. On Linux, run 'google-chrome --version' or 'chromium --version'.
    Affected if The reported version is lower than 148.0.7778.96
  3. Confirm Chrome is the affected browser
    Ensure the Chrome installation being checked is the standard Google Chrome (not Chromium builds or other browsers based on Chrome). Check the browser name in About page or the executable properties.
    Affected if The browser is Google Chrome and the version is below 148.0.7778.96
  4. Review Chrome's Speech Recognition component
    This vulnerability exists in Chrome's built-in Speech Recognition feature (used for voice input in web pages). No specific configuration check is needed - the vulnerability is present in the Speech component code of affected versions.
    Affected if Any Google Chrome version below 148.0.7778.96 contains the vulnerable Speech component code

You are affected if you are running any version of Google Chrome older than 148.0.7778.96, as the race condition in the Speech component exists in those versions regardless of configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 148.0.7778.96 or later
Fixed in 148.0.7778.96
Interim mitigation

Update Google Chrome to version 148.0.7778.96 or later. Until updated, restrict or disable Chrome usage in environments where the renderer process could be compromised.

Recommended fix High confidence

Chrome 148.0.7778.96 or later

  1. 1. Open Google Chrome browser on your system
  2. 2. Click the three-dot menu in the top-right corner and select 'Settings', or navigate to chrome://settings
  3. 3. Scroll down and click 'About Chrome' in the left sidebar
  4. 4. Chrome will automatically check for updates and download version 148.0.7778.96 or later if available
  5. 5. Once the update is downloaded, click 'Restart' to apply the update
  6. 6. Alternatively, manually download the latest Chrome version from google.com/chrome and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7960 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7960 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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