dbcve.org
ChromeWeb browser · Google

CVE-2026-9881

CRITICAL · 9.0 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 148.0.7778.216 or later.
See remediation →
99/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Bluetooth in Google Chrome on Mac prior to 148.0.7778.216 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted Chrome Extension. (Chromium security severity: Critical)

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 use-after-free vulnerability exists in the Bluetooth component of Google Chrome on macOS versions prior to 148.0.7778.216. Attackers can exploit this by tricking users into installing a malicious Chrome extension, potentially allowing sandbox escape and arbitrary code execution.

MitigationUpdate Google Chrome to version 148.0.7778.216 or later. Enforce restriction policies to prevent installation of untrusted extensions and deploy Chrome updates via MDM or patch management.

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

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
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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 installed Chrome version on macOS
    Open Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version OR navigate to Chrome > About Google Chrome in the menu bar
    Affected if The version number displayed is less than 148.0.7778.216
  2. Confirm macOS platform
    Run 'uname -a' in Terminal or check System Settings > About > macOS version
    Affected if The system is running macOS (the vulnerability only affects Chrome on macOS)
  3. Verify Bluetooth is enabled
    Go to System Settings > Bluetooth or run 'blueutil -p' in Terminal to check Bluetooth status
    Affected if Bluetooth is turned ON - the vulnerable Bluetooth component is active
  4. Check extension installation policy
    Open Chrome and navigate to chrome://extensions, or check if Enterprise policies are configured by running: defaults read com.google.Chrome ExtensionInstallWhitelist in Terminal
    Affected if Extensions can be installed without restrictions (no whitelist policy enforced) - the attack requires user installation of a malicious extension

You are affected if you are running Google Chrome on macOS with a version lower than 148.0.7778.216, have Bluetooth enabled, and users can install extensions without administrative controls.

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.216 or later
Fixed in 148.0.7778.216
Interim mitigation

Update Google Chrome to version 148.0.7778.216 or later. Enforce restriction policies to prevent installation of untrusted extensions and deploy Chrome updates via MDM or patch management.

Recommended fix High confidence

148.0.7778.216

  1. 1. Open Google Chrome on Mac
  2. 2. Click on the Chrome menu in the top-left corner
  3. 3. Select 'About Google Chrome' from the dropdown menu
  4. 4. Chrome will automatically check for updates
  5. 5. If version 148.0.7778.216 or later is available, click 'Update Google Chrome'
  6. 6. Wait for the download and installation to complete
  7. 7. Click 'Relaunch' to restart Chrome and apply the update

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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