ChromeWeb browser · Google
CVE-2026-9882
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 · uneditedInteger overflow in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Critical)
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 · moderate confidenceInteger overflow vulnerability in ANGLE graphics library allows a remote attacker to bypass cross-origin restrictions and leak sensitive data from other origins by tricking users into visiting a crafted HTML page.
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
< 148.0.7778.216< 148.0.7778.215CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionNavigate to chrome://settings/help or type 'chrome://version' in the address bar to view the installed Chrome versionAffected if The displayed version is less than 148.0.7778.216 (or 148.0.7778.215 depending on platform)
-
Confirm Chrome channel and buildCheck the full version string in chrome://version - note the major, minor, and build numbers along with any channel indicators (stable, beta, dev, canary)Affected if The build number is below 7778.216 on the stable channel or below 7778.215 on other channels
-
Verify WebGL is enabledGo to chrome://settings and search for 'Hardware acceleration' or visit a WebGL-enabled site and inspect whether WebGL context initializes (WebGL relies on ANGLE)Affected if WebGL hardware acceleration is enabled - this is required for the ANGLE integer overflow to be exploitable
-
Confirm ANGLE renderer is in useOpen chrome://gpu and look at the 'WebGL' or 'Rendering' section - ANGLE (Accelerated Native Windows Rendering Environment) is listed as the WebGL driver when the vulnerability appliesAffected if ANGLE is listed as the WebGL rendering backend, indicating the affected component is active
A user is affected if their Chrome version is below 148.0.7778.216 (or 148.0.7778.215) and WebGL with ANGLE is enabled in the browser.
Generated from the published advisory. Verify against your own configuration.
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 · scoped148.0.7778.215148.0.7778.216
Update Google Chrome to version 148.0.7778.216 or later to patch the integer overflow vulnerability in ANGLE.
Chrome 148.0.7778.216 or later
- Open Google Chrome
- Navigate to chrome://settings/help or go to Settings > About Chrome
- Chrome will automatically check for updates
- If update to version 148.0.7778.216 or later is available, click 'Update Google Chrome'
- Restart Chrome to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9882 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9882 in production — separate from our analysis above.
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.
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.
- 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