ChromeWeb browser · Google
CVE-2026-11637
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 Views in Google Chrome on Mac prior to 149.0.7827.103 allowed a remote attacker to execute arbitrary code 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 confidenceUse-after-free vulnerability in Google Chrome's Views component on Mac systems affecting versions prior to 149.0.7827.103. A remote attacker can exploit this memory corruption flaw via a crafted HTML page to achieve arbitrary code execution.
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.
-
Check installed Chrome version on macOSOpen Chrome, click the Chrome menu in the menu bar, and select 'About Google Chrome'. Alternatively, run this command in Terminal: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --versionAffected if The displayed version number is lower than 149.0.7827.103 (for example, 149.0.7827.100 or earlier)
-
Confirm the operating system is macOSClick the Apple menu in the top-left corner and select 'About This Mac', or run 'uname -a' in TerminalAffected if The system is running macOS and the Chrome version from step 1 is below 149.0.7827.103. This CVE specifically affects macOS only.
-
Verify Chrome is the default browser (optional context)Open System Settings > Desktop & Dock (or System Preferences on older macOS) and check the 'Default web browser' settingAffected if Chrome is set as the default browser. While not required for the vulnerability, users with Chrome as default are more likely to encounter malicious pages.
You are affected if Google Chrome on macOS is running a version earlier than 149.0.7827.103, as the use-after-free in the Views component can be triggered by visiting a specially crafted HTML page.
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 to version 149.0.7827.103 or later on all affected Mac systems. In enterprise environments, deploy the update via patch management infrastructure and verify successful installation.
149.0.7827.103 or later
- Open Google Chrome on your Mac
- Click on the Chrome menu in the menu bar and select 'About Google Chrome'
- Chrome will automatically check for updates
- If an update is available, click 'Update Google Chrome'
- Restart Chrome to complete the installation
- Verify the version by going to 'About Google Chrome' again and confirm the version number is 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
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11637 — 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-11637 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