ChromeWeb browser · Google
CVE-2026-10907
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 · uneditedOut of bounds write in ANGLE in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to potentially exploit heap corruption 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 confidenceOut-of-bounds write vulnerability in ANGLE (a graphics library providing OpenGL ES emulation) in Google Chrome prior to version 149.0.7827.53. A remote attacker can exploit this via a crafted HTML page to write data beyond allocated buffer boundaries, leading to heap corruption and potential arbitrary code execution.
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
< 149.0.7827.53CVSS 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 Google Chrome versionOpen Chrome, click the three-dot menu > Help > About Google Chrome. The version number is displayed on this page.Affected if Version is less than 149.0.7827.53 (e.g., 148.x.x.x or earlier)
-
Verify WebGL status (ANGLE dependency)Open chrome://settings in the address bar, search for 'Hardware acceleration' or navigate to Advanced > System. Confirm if hardware acceleration is enabled.Affected if WebGL is used when hardware acceleration is enabled, which enables ANGLE graphics rendering
-
Confirm Chrome update channelIn chrome://settings, look for the update status under 'About Chrome', or check if the browser is set to automatically update.Affected if Browser is on stable, beta, or dev channel with an older version than 149.0.7827.53
-
Check for active renderer processes using ANGLEOpen chrome://process-internals, look for 'GPU Process' or 'Renderer' entries. ANGLE is used for WebGL graphics rendering.Affected if GPU process is active and rendering WebGL content
You are affected if Google Chrome version is below 149.0.7827.53 and WebGL/graphics acceleration is enabled, as the ANGLE out-of-bounds write requires the graphics layer to be active.
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 · scoped149.0.7827.53
Update Google Chrome to version 149.0.7827.53 or later. Organizations should deploy this update through enterprise patch management and verify compliance across managed endpoints.
Chrome 149.0.7827.53 or later
- 1. Verify current Chrome version by navigating to chrome://settings/help or checking About Google Chrome in the menu
- 2. If the installed version is earlier than 149.0.7827.53, initiate an update by clicking 'Update Google Chrome'
- 3. Restart Chrome to apply the update
- 4. Verify the update was successful by checking the version again - it should show 149.0.7827.53 or later
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
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 locallyCheck whether your project pulls in CVE-2026-10907 — 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-10907 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