dbcve.org
ChromeWeb browser · Google

CVE-2026-9928

HIGH · 8.8 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 148.0.7778.216 or later.
See remediation →
95/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
Out of bounds read in ANGLE in Google Chrome on Windows prior to 148.0.7778.216 allowed a remote attacker to execute arbitrary code 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

Out-of-bounds read vulnerability in ANGLE (a graphics translation layer) in Google Chrome on Windows allows remote code execution via a crafted HTML page. The vulnerability exists in versions prior to 148.0.7778.216.

MitigationUpdate Google Chrome to version 148.0.7778.216 or later to remediate this vulnerability. Organizations should ensure automatic updates are enabled or push the update via patch management.

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:< 148.0.7778.216

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
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 checks

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

  1. Confirm Google Chrome is installed on Windows
    Check for chrome.exe in the default installation directories: C:\Program Files\Google\Chrome\Application\ or C:\Program Files (x86)\Google\Chrome\Application\. Alternatively, run 'Get-Process chrome -ErrorAction SilentlyContinue' in PowerShell to see if Chrome is currently running.
    Affected if Chrome is not installed on the Windows system
  2. Obtain the installed Google Chrome version number
    Open Google Chrome and navigate to chrome://settings/help to view the version, or run 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' from Command Prompt, or query the registry using PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Google\Chrome\BLBeacon' | Select-Object -ExpandProperty version
    Affected if Unable to retrieve the version number from Chrome, the version page, or the registry
  3. Compare the installed version against the affected range
    Parse the retrieved version number and compare it numerically to 148.0.7778.216. Any version lower than 148.0.7778.216 (such as 148.0.7778.0, 147.0.5446.0, etc.) falls within the affected range.
    Affected if The installed version is less than 148.0.7778.216 (for example, 148.0.7778.0 or any earlier major.minor.patch version)
  4. Identify if ANGLE graphics library is in use
    Check if WebGL is enabled in Chrome by navigating to chrome://settings, searching for 'Hardware acceleration' or 'WebGL', or inspect running Chrome processes for ANGLE-related DLLs (libEGL.dll, libGLESv2.dll) in the Chrome application directory.
    Affected if WebGL or hardware acceleration is enabled, which allows ANGLE to process graphics data and enables the vulnerable code path

The system is affected if Google Chrome on Windows has a version number lower than 148.0.7778.216 and has WebGL or hardware acceleration enabled, allowing the ANGLE graphics library to process crafted graphics data.

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 148.0.7778.216 or later
Fixed in 148.0.7778.216
Interim mitigation

Update Google Chrome to version 148.0.7778.216 or later to remediate this vulnerability. Organizations should ensure automatic updates are enabled or push the update via patch management.

Recommended fix High confidence

148.0.7778.216 or later (Chrome stable channel)

  1. Open Chrome and navigate to Settings > About Chrome to check the current version
  2. If the installed version is earlier than 148.0.7778.216, click 'Update Google Chrome' to install the latest version
  3. Restart the browser after the update completes
  4. Verify the update was successful by returning to Settings > About Chrome and confirming version 148.0.7778.216 or later is installed

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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