ChromeWeb browser · Google
CVE-2026-10019
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: Medium)
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 confidenceInteger overflow in ANGLE (Almost Native Graphics Layer Engine) in Google Chrome prior to version 148.0.7778.216 allows a remote attacker to leak cross-origin data via a specially crafted HTML page. The vulnerability stems from improper integer handling in the graphics rendering component, potentially enabling violation of same-origin policy.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome versionNavigate to chrome://settings/help or click Help > About Google Chrome to view the version numberAffected if Version is below 148.0.7778.215 or 148.0.7778.216 (check both branch numbers)
-
Verify Chrome channel and buildIn chrome://settings/help, confirm whether you are on Stable, Beta, Dev, or Canary channel and note the full version string including build numberAffected if The build number is lower than 7778.215 or 7778.216 on any channel
-
Confirm ANGLE library presenceANGLE is bundled with Chrome by default. Visit chrome://gpu and look for ' ANGLE ' or 'Graphics: ANGLE' in the GPU information sectionAffected if ANGLE is listed as active and Chrome version is in the vulnerable range
-
Check for enterprise policy overridesIf managed by an organization, check chrome://policy for any BrowserUpdatePolicy restrictions that may prevent automatic version updatesAffected if Enterprise policies block updates and Chrome version falls below the fixed releases
You are affected if your Google Chrome version is below 148.0.7778.216 (or 148.0.7778.215 on certain branches) and the ANGLE graphics library is in use, which is the default configuration.
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 and Chromium-based browsers to version 148.0.7778.216 or later. Organizations should deploy browser updates through their patch management systems.
Chrome 148.0.7778.216 or later
- Open Google Chrome
- Navigate to Help > About Google Chrome
- Verify the current version number
- If version is below 148.0.7778.216, Chrome will automatically check for updates
- Click 'Update Google Chrome' if an update is available
- Restart the browser to apply the update
- Alternatively, download the latest stable Chrome from the official Google website
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-10019 — 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-10019 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