ChromeWeb browser · Google

CVE-2026-8523

HIGH · 8.3 CVSS v3.1 Published 2026-05-14

Fix available

A fix is available. Upgrade to 148.0.7778.168 or later.

See remediation →

90/100

Remediation priority · Urgent

Remotely reachable No privileges

Official description

NVD · unedited

Use after free in Mojo in Google Chrome prior to 148.0.7778.168 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

Technical summary

dbcve analysis · moderate confidence

Use-after-free vulnerability in Chrome's Mojo component (inter-process communication) allows a remote attacker with a compromised renderer process to potentially escape the sandbox via a specially crafted HTML page.

MitigationUpdate Google Chrome to version 148.0.7778.168 or later. In enterprise environments, deploy the update via group policy or endpoint management tools and verify complete coverage.

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.168

CVSS breakdown

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?

dbcve checks

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

Verify Google Chrome is installed

Check for Chrome executable or application: Windows: look for chrome.exe in Program Files or registry; macOS: check /Applications/Google Chrome.app; Linux: check for google-chrome package or /usr/bin/google-chrome

Affected if Chrome is not installed on the system
Determine installed Chrome version

Open chrome://version in Chrome browser, or run: Windows: reg query 'HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome' /v Version; macOS: defaults read /Applications/Google\ Chrome.app/Contents/Info.plist CFBundleShortVersionString; Linux: google-chrome --version or rpm -q google-chrome

Affected if Unable to retrieve version number, but Chrome is present
Compare version to affected range

Compare the installed version number to 148.0.7778.168 using semantic version comparison

Affected if Installed version is less than 148.0.7778.168 (e.g., 148.0.7778.100, 148.0.7777.200, etc.)
Confirm Chrome is actively used

Check for recent Chrome browser activity or profile data: Windows: %LOCALAPPDATA%\Google\Chrome\User Data; macOS: ~/Library/Application Support/Google/Chrome; Linux: ~/.config/google-chrome

Affected if Chrome profiles or recent browser activity exist, indicating active usage of the vulnerable component

User is affected if Google Chrome is installed with a version below 148.0.7778.168 and the browser is being actively used, as the vulnerability is triggered through specially crafted HTML pages loaded in the renderer process.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 148.0.7778.168 or later

Fixed in 148.0.7778.168

Interim mitigation

Update Google Chrome to version 148.0.7778.168 or later. In enterprise environments, deploy the update via group policy or endpoint management tools and verify complete coverage.

Recommended fix High confidence

Chrome 148.0.7778.168

Open Chrome and navigate to Settings > Help > About Google Chrome to check the current version
If the version is below 148.0.7778.168, Chrome will automatically check for and download the update
Restart Chrome to apply the update
Verify the version is now 148.0.7778.168 or later by returning to Settings > 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

Consultation4.0 h
Implementation6.0 h
Testing2.0 h
Review / QA2.0 h

14.0 hours of engineering $2,540

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,064.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-8523 — 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.comProductVendor Advisory
issues.chromium.orgPermissions Required
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-8523?

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.168 or later

Severity 8.3 High

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Chrome

Remediation

A high-priority fix

Fix this in Chrome 14 hrs · Moderate

Typical engagement from $2,540

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-8523 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