dbcve.org
ChromeWeb browser · Google

CVE-2026-8586

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-14
Fix available
A fix is available. Upgrade to 148.0.7778.168 or later.
See remediation →
58/100
Remediation priority · Elevated
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 prior to 148.0.7778.168 allowed a local attacker to bypass discretionary access control 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 vulnerability in Google Chrome's Chromoting (remote desktop) feature prior to version 148.0.7778.168 allows a local attacker to bypass discretionary access control through a malicious file. The attacker would need to convince a user to interact with the file locally, potentially allowing unauthorized access or privilege escalation.

MitigationUpdate Google Chrome to version 148.0.7778.168 or later. Organizations should verify all endpoints have the patched version installed.

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.168

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

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

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. Verify Google Chrome is installed
    Check for Chrome installation in typical locations: Windows (C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe), macOS (/Applications/Google Chrome.app), or Linux (/usr/bin/google-chrome or /usr/bin/chromium-browser). On Windows, also query the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome.
    Affected if Chrome is not found on the system, this CVE does not apply.
  2. Determine installed Chrome version
    On Windows, run: "C:\Program Files\Google\Chrome\Application\chrome.exe" --version or right-click chrome.exe, select Properties, view Details tab for File Version. On macOS, run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version or right-click app, Get Info. On Linux, run: google-chrome --version or chromium-browser --version.
    Affected if Version number is lower than 148.0.7778.168 (e.g., 147.x.x.x or earlier).
  3. Confirm Chromoting feature presence
    Chrome's remote desktop (Chromoting) is built into the Chrome browser. Check if the user has access to remoting features by opening chrome://settings and searching for 'remote desktop' or navigating to chrome://remoting. Also check for the Chrome Remote Desktop extension or app components in the installation directory under resources/remoting.
    Affected if Chromoting components are present and accessible on the system.
  4. Check for recent Chrome usage
    Review browser history or recent documents to see if the user has opened untrusted files locally, as the attack requires user interaction with a malicious file. On Windows, check Recent Items (shell:recent) or the user's Downloads folder for suspicious files.
    Affected if Users have been opening files from untrusted sources locally.

The environment is affected if Google Chrome is installed with a version lower than 148.0.7778.168 and the Chromoting feature is present and accessible.

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.168 or later
Fixed in 148.0.7778.168
Interim mitigation

Update Google Chrome to version 148.0.7778.168 or later. Organizations should verify all endpoints have the patched version installed.

Recommended fix High confidence

Chrome 148.0.7778.168 or later stable release

  1. Open Google Chrome browser
  2. Navigate to Settings by clicking the three-dot menu in the top-right corner
  3. Scroll down and click on 'Help'
  4. Click on 'About Google Chrome'
  5. Chrome will automatically check for updates and display the current version
  6. If an update is available, click 'Update Google Chrome' (or wait for it to download automatically)
  7. After the update completes, click 'Relaunch' to restart the browser
  8. Alternatively, download the latest Chrome version directly from the official Chrome download page (google.com/chrome) to ensure you have version 148.0.7778.168 or later
Caveat Chrome security updates typically have minimal breaking changes; however, ensure any enterprise policies or extensions are compatible with the new version before mass deployment

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8586 — 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-8586 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