dbcve.org
ChromeWeb browser · Google

CVE-2026-9908

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 148.0.7778.216 or later.
See remediation →
72/100
Remediation priority · Elevated
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 prior to 148.0.7778.216 allowed a remote attacker to obtain potentially sensitive information from process memory 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

An out-of-bounds read vulnerability exists in ANGLE (a graphics library layer) in Google Chrome versions prior to 148.0.7778.216. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, allowing the attacker to read memory beyond allocated buffer boundaries and potentially expose sensitive process memory information.

MitigationUpdate Google Chrome to version 148.0.7778.216 or later to patch the vulnerability. Organizations should deploy the update via standard patch management processes and ensure end-users restart their browsers.

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
None
Availability
None

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

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. Check installed Google Chrome version
    Open chrome://version in the Chrome address bar or click Chrome menu > Help > About Google Chrome. Note the version number displayed.
    Affected if The displayed version is less than 148.0.7778.216 (for example, 148.0.7778.200 or earlier)
  2. Verify WebGL is enabled (ANGLE graphics layer)
    Navigate to chrome://settings in Chrome, search for 'WebGL', and confirm the 'Hardware acceleration, when available' option or WebGL is not explicitly disabled. Alternatively, visit a WebGL-enabled site to confirm graphics functionality works.
    Affected if WebGL or hardware acceleration is enabled (this is the default state; the vulnerability applies when ANGLE is in use)
  3. Confirm Chrome is being used as the browser
    Check that the affected software is Google Chrome itself (not Chromium-based browsers like Edge, Brave, or Vivaldi which maintain separate version sequences).
    Affected if The browser is Google Chrome with a version below 148.0.7778.216

You are affected if you are running any version of Google Chrome prior to 148.0.7778.216 with WebGL or hardware acceleration enabled (the default configuration).

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 patch the vulnerability. Organizations should deploy the update via standard patch management processes and ensure end-users restart their browsers.

Recommended fix High confidence

148.0.7778.216 or later

  1. Open Google Chrome and click the three-dot menu icon in the top-right corner
  2. Select 'Help' from the dropdown menu, then click 'About Google Chrome'
  3. Chrome will check for updates and display the current version
  4. If a version lower than 148.0.7778.216 is shown, click 'Update Google Chrome' to download and install the fix
  5. After updating, click 'Relaunch' to restart Chrome and apply the changes

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-9908 — 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-9908 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