ChromeWeb browser · Google

CVE-2026-9886

CRITICAL · 9.6 CVSS v3.1 Published 2026-05-28

Fix available

A fix is available. Upgrade to 148.0.7778.216 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges

Official description

NVD · unedited

Use after free in Base in Google Chrome on Mac prior to 148.0.7778.216 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

Technical summary

dbcve analysis · high confidence

A use-after-free vulnerability exists in the Base component of Google Chrome on macOS before version 148.0.7778.216. The flaw allows a remote attacker to execute arbitrary code by tricking users into visiting a specially crafted HTML page, potentially leading to a sandbox escape that could compromise the entire system.

MitigationImmediately update Google Chrome for Mac to version 148.0.7778.216 or later. Organizations should deploy this update enterprise-wide using their MDM or patch management tools and verify completion across all managed macOS endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ChromeWeb browser

Affected:< 148.0.7778.216

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: Required
Scope: Changed
Confidentiality: High
Integrity: High
Availability: High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Verify macOS is the operating system

Check system information via System Settings > About or run 'uname -a' in Terminal. This vulnerability only affects Chrome on macOS.

Affected if The system is not running macOS (the vulnerability does not apply to Windows, Linux, or other platforms).
Confirm Google Chrome is installed

Look for Google Chrome in /Applications/ folder or run 'ls /Applications | grep -i chrome' in Terminal.

Affected if Google Chrome is not installed (no Chrome, no vulnerability).
Determine installed Chrome version

Open Chrome, click the three-dot menu > Help > About Google Chrome, or run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in Terminal.

Affected if The displayed version number is lower than 148.0.7778.216 (e.g., 148.0.7778.100, 147.x.x.x, etc.).
Verify the specific version falls in affected range

Compare the installed version string against the vulnerable range: any version prior to 148.0.7778.216 on macOS is affected.

Affected if Installed version is < 148.0.7778.216 and the browser is used to visit untrusted HTML content.

You are affected if running Google Chrome on macOS with a version number lower than 148.0.7778.216.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 148.0.7778.216 or later

Fixed in 148.0.7778.216

Interim mitigation

Immediately update Google Chrome for Mac to version 148.0.7778.216 or later. Organizations should deploy this update enterprise-wide using their MDM or patch management tools and verify completion across all managed macOS endpoints.

Recommended fix High confidence

148.0.7778.216 or later (Chrome stable release)

Open Google Chrome browser
Click on the menu icon (three dots) in the top-right corner
Select 'Help' from the dropdown menu
Click on 'About Google Chrome'
The browser will check for updates automatically
If an update is available, click 'Update Google Chrome'
Restart the browser to complete the installation
Verify the version is 148.0.7778.216 or later by returning to About Google Chrome

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

Fix this in Chrome Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing3.0 h
Review / QA2.0 h

17.0 hours of engineering $3,050

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

chromereleases.googleblog.comRelease Notes
issues.chromium.orgPermissions Required
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9886 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-9886?

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.

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

At a glance

A fix existsUpgrade to 148.0.7778.216 or later

Severity 9.6 Critical

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Chrome

Remediation

A high-priority fix

Fix this in Chrome 17 hrs · Moderate

Typical engagement from $3,050

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-9886 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References