ChromeWeb browser · Google
CVE-2026-11698
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 · uneditedUse after free in Bluetooth in Google Chrome on Mac prior to 149.0.7827.103 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
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 confidenceA use-after-free vulnerability in Google Chrome's Bluetooth component on macOS allows a remote attacker to exploit heap corruption through a specially crafted HTML page. The vulnerability exists in versions prior to 149.0.7827.103 and enables potential arbitrary code execution via heap manipulation.
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
< 149.0.7827.103CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Google Chrome is installed on macOSOpen Terminal and run: ls /Applications/ | grep -i chrome or check /Applications/Google Chrome.app existsAffected if Google Chrome is present on the system
-
Determine the installed Google Chrome versionOpen Chrome, go to Help > About Google Chrome, or run in Terminal: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --versionAffected if The displayed version is lower than 149.0.7827.103
-
Confirm macOS platformRun in Terminal: uname -s to verify the system is Darwin (macOS)Affected if The system is running macOS (Darwin kernel)
-
Check if Bluetooth is enabled and accessibleIn Chrome, navigate to chrome://bluetooth-internals/ or check macOS System Preferences > Bluetooth is turned onAffected if Bluetooth is enabled, allowing the vulnerable code path to be reached
A user is affected if Google Chrome version 149.0.7827.103 or later is NOT installed on macOS and Bluetooth is accessible to the browser.
Generated from the published advisory. Verify against your own configuration.
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 · scoped149.0.7827.103
Update Google Chrome for Mac to version 149.0.7827.103 or later to patch the Bluetooth use-after-free vulnerability.
Chrome 149.0.7827.103 or later
- Open Google Chrome on the Mac system
- Click on the Chrome menu (three dots) in the top-right corner
- Select 'Help' then 'About Google Chrome'
- The browser will check for updates and display the current version
- If a version lower than 149.0.7827.103 is shown, click 'Update Google Chrome'
- Wait for the download to complete and restart Chrome when prompted
- Verify the version after restart shows 149.0.7827.103 or later via Help > About Google Chrome
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
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 locallyCheck whether your project pulls in CVE-2026-11698 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11698 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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