dbcve.org
ChromeWeb browser · Google

CVE-2026-11635

HIGH · 8.3 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 149.0.7827.103 or later.
See remediation →
90/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 Bluetooth in Google Chrome on Mac prior to 149.0.7827.103 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (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

Use-after-free vulnerability in the Bluetooth component of Google Chrome on macOS versions prior to 149.0.7827.103. A remote attacker who has already compromised the renderer process can exploit this UAF via a malicious crafted HTML page to escape the sandbox and execute code outside the renderer's isolation boundaries.

MitigationUpdate Google Chrome to version 149.0.7827.103 or later. In enterprise environments, ensure automated patch deployment or enforce the update via group policy/MDM solutions.

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:< 149.0.7827.103

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Verify Google Chrome is installed
    Open Terminal and run: ls /Applications/ | grep -i chrome or check /Applications/Google Chrome.app exists
    Affected if Google Chrome is not found in Applications folder - not applicable
  2. Check the installed Chrome version on macOS
    Open Terminal and run: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version OR click Chrome menu > About Google Chrome
    Affected if Version number returned is lower than 149.0.7827.103
  3. Confirm the operating system is macOS
    Open Terminal and run: sw_vers or click Apple menu > About This Mac
    Affected if Operating system is not macOS - this specific CVE does not apply to other platforms
  4. Verify the Bluetooth component is in use
    Check if Bluetooth is enabled: system_profiler SPBluetoothDataType or go to System Settings > Bluetooth on macOS
    Affected if Bluetooth is disabled - the attack surface may be reduced but the vulnerable code path still exists in affected versions

User is affected if Google Chrome version is below 149.0.7827.103 on macOS, regardless of Bluetooth state, since the vulnerable Bluetooth component code is present in the build.

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 149.0.7827.103 or later
Fixed in 149.0.7827.103
Interim mitigation

Update Google Chrome to version 149.0.7827.103 or later. In enterprise environments, ensure automated patch deployment or enforce the update via group policy/MDM solutions.

Recommended fix High confidence

149.0.7827.103

  1. 1. Open Google Chrome on your Mac device
  2. 2. Click on the Chrome menu in the top-left corner of the browser window
  3. 3. Select 'About Google Chrome' from the dropdown menu
  4. 4. Chrome will automatically check for updates and display the current version
  5. 5. If an update is available, click 'Update Google Chrome'
  6. 6. After the update downloads, click 'Relaunch' to restart Chrome and apply the update
  7. 7. Verify the version by returning to About Google Chrome - it should show version 149.0.7827.103 or later

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.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-11635 — 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-11635 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