dbcve.org
ChromeWeb browser · Google

CVE-2026-8587

HIGH · 8.8 CVSS v3.1 Published 2026-05-14
Fix available
A fix is available. Upgrade to 148.0.7778.168 or later.
See remediation →
95/100
Remediation priority · Urgent
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
Use after free in Extensions in Google Chrome on Mac prior to 148.0.7778.168 allowed an attacker who convinced a user to install a malicious extension to execute arbitrary code via a crafted Chrome Extension. (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

Use-after-free vulnerability in Chrome's extension system on Mac OS allows a malicious extension to achieve arbitrary code execution. The attack requires user interaction to install the malicious extension.

MitigationUpdate Google Chrome to version 148.0.7778.168 or later on all affected Mac systems, and enforce organizational policies restricting extension installation to trusted sources only.

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

CVSS:3.1/AV:N/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. Check if Google Chrome is installed on Mac
    Open Terminal and run: ls /Applications/ | grep -i chrome
    Affected if Google Chrome is not found in /Applications/ directory - not affected if not installed
  2. Determine installed Chrome version
    Open Terminal and run: defaults read /Applications/Google\ Chrome.app/Contents/Info CFBundleShortVersionString
    Affected if Version number is returned - proceed to next check
  3. Compare against affected version range
    Compare the installed version to 148.0.7778.168. The installed version is affected if it is lower (e.g., 148.0.7778.100, 147.x.x.x, etc.)
    Affected if Installed version is less than 148.0.7778.168 - system is affected
  4. Verify operating system is Mac OS
    Run: uname -s in Terminal. Confirm output is 'Darwin'
    Affected if OS is Darwin (Mac OS) - vulnerability applies only on Mac systems; if OS is Linux or Windows, not affected by this specific CVE
  5. Check if extensions can be installed
    In Chrome, go to chrome://extensions or chrome://policy to review extension management settings
    Affected if Extension installation is allowed or no organizational policy blocks it - vulnerability is exploitable if a user installs a malicious extension

System is affected if Google Chrome version is less than 148.0.7778.168 on Mac OS, and users have the ability to install extensions.

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 on all affected Mac systems, and enforce organizational policies restricting extension installation to trusted sources only.

Recommended fix High confidence

148.0.7778.168 or later

  1. Open Google Chrome browser
  2. Click on the three-dot menu (Settings) in the top-right corner
  3. Navigate to 'Help' > 'About Google Chrome'
  4. The browser will automatically check for updates
  5. If version 148.0.7778.168 or later is available, click 'Update Google Chrome'
  6. Restart the browser to complete the update
  7. Verify the update by returning to 'About Google Chrome' and confirming the version number
Caveat Chrome auto-updates are generally low-risk; however, some older extensions or websites may experience temporary compatibility issues until developers update them

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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