dbcve.org
ChromeWeb browser · Google

CVE-2026-7994

HIGH · 7.8 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 148.0.7778.96 or later.
See remediation →
81/100
Remediation priority · High
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
Inappropriate implementation in Chromoting in Google Chrome on Windows prior to 148.0.7778.96 allowed a local attacker to perform OS-level privilege escalation via a malicious file. (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 local privilege escalation vulnerability exists in Google Chrome's Chromoting (remote desktop) feature on Windows versions prior to 148.0.7778.96. A local attacker can exploit this by tricking a user into opening a specially crafted malicious file, potentially elevating privileges from user-level to OS-level access.

MitigationUpdate Google Chrome for Windows to version 148.0.7778.96 or later to patch this vulnerability. Organizations should deploy the browser update through their patch management systems.

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

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

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

  1. Locate Chrome installation on Windows
    Check for chrome.exe in typical installation directories: C:\Program Files\Google\Chrome\Application\ or C:\Program Files (x86)\Google\Chrome\Application\. You can also search for chrome.exe using File Explorer or the command: dir /s C:\chrome.exe
    Affected if Chrome is not installed on the system - if absent, this CVE does not apply
  2. Determine installed Chrome version
    Right-click chrome.exe, select Properties, then view the Details tab to see the File Version. Alternatively, open Command Prompt, navigate to the Chrome directory, and run: chrome.exe --version
    Affected if The version number displayed is less than 148.0.7778.96 - this indicates a potentially vulnerable version
  3. Verify Chromoting feature presence
    Check if Chromoting has been configured or enabled. Look for the 'Chromoting' or 'Remote Desktop' feature in Chrome settings (chrome://settings), or check for related registry keys under HKCU\Software\Google\Chrome\ or HKLM\Software\Google\Chrome\ for Chromoting-related entries
    Affected if Chromoting is explicitly enabled or has been used previously - the vulnerability requires this feature to be accessible for exploitation
  4. Check for Chromoting service or binary
    Search for Meecd.exe or Chrome Remote Desktop host service files in the system. These are typically found in %LOCALAPPDATA%\Google\Chrome Remote Desktop\ or installed as a Windows service. Use File Explorer to search these locations
    Affected if Chromoting host components are installed on the system - exploitation requires these binaries to be present

You are affected if Chrome for Windows is installed with a version prior to 148.0.7778.96 AND the Chromoting feature or its host components are present on the system, creating an attack surface for local privilege escalation.

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 for Windows to version 148.0.7778.96 or later to patch this vulnerability. Organizations should deploy the browser update through their patch management systems.

Recommended fix High confidence

Chrome 148.0.7778.96 or later for Windows

  1. Open Google Chrome on the affected Windows machine
  2. Click the three-dot menu icon in the top-right corner of the browser
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. The browser will automatically check for updates and download version 148.0.7778.96 or later
  6. Wait for the download and installation to complete
  7. Click 'Relaunch' or restart Chrome manually to apply the update
  8. Verify the version by returning to Help > About Google Chrome and confirming the version is 148.0.7778.96 or higher
Caveat Chrome updates typically have minimal breaking changes; some older extensions or enterprise policies may require re-validation

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-7994 — 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-7994 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