dbcve.org
ChromeWeb browser · Google

CVE-2026-11677

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
Race in Network in Google Chrome on Mac prior to 149.0.7827.103 allowed a remote attacker who had compromised the network process to potentially perform a sandbox escape 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 confidence

This is a race condition vulnerability in Google Chrome's network process on macOS. A remote attacker who has already compromised the network process can exploit a race condition via a crafted HTML page to potentially escape the browser's sandbox. The vulnerability affects versions prior to 149.0.7827.103.

MitigationUpdate Google Chrome to version 149.0.7827.103 or later on all affected macOS systems. Organizations should ensure automatic updates are enabled or push the update through their patch management infrastructure.

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. Confirm Mac OS environment
    Check if the system is running Mac OS by going to Apple menu > About This Mac, or running 'uname -s' in Terminal which should return 'Darwin'
    Affected if This vulnerability only affects Chrome on Mac OS; Windows and Linux users are not affected by this specific flaw
  2. Locate Google Chrome installation
    Check if Google Chrome is installed in /Applications/ or run 'ls /Applications/ | grep -i chrome' in Terminal
    Affected if Chrome must be installed for this vulnerability to apply
  3. Determine installed Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome, or visit chrome://settings/help, or run: defaults read /Applications/Google\ Chrome.app/Contents/Info.plist CFBundleShortVersionString
    Affected if The exact version number displayed must be compared against the affected range
  4. Compare version against affected range
    Check if the installed version is less than 149.0.7827.103. Version format typically appears as '149.0.7827.103' or major version like 148.x
    Affected if If the installed version is 148.x or any version below 149.0.7827.103, the system falls within the affected range

If running Google Chrome on Mac OS with a version lower than 149.0.7827.103, the environment is affected by this vulnerability.

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 on all affected macOS systems. Organizations should ensure automatic updates are enabled or push the update through their patch management infrastructure.

Recommended fix High confidence

Chrome version 149.0.7827.103 or later

  1. 1. Open Google Chrome on the affected Mac system
  2. 2. Click on the Chrome menu (three dots) in the top-right corner
  3. 3. Select 'Help' from the dropdown menu
  4. 4. Click 'About Google Chrome'
  5. 5. Chrome will automatically check for updates and display the current version
  6. 6. If an update is available, click 'Update Google Chrome' button
  7. 7. After the update downloads, click 'Relaunch' to restart the browser and apply the update
  8. 8. 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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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