ChromeWeb browser · Google
CVE-2026-10974
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 · uneditedInsufficient validation of untrusted input in ANGLE in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to potentially perform a sandbox escape 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 confidenceA validation flaw in the ANGLE graphics engine component of Google Chrome versions prior to 149.0.7827.53 allows remote attackers to inject untrusted input through maliciously crafted HTML pages, potentially escaping the browser's security sandbox to execute code on the host system.
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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 if Google Chrome is installedOn Windows, check for Chrome in Program Files or via Registry. On macOS, check /Applications/Google Chrome.app. On Linux, check /usr/bin/google-chrome or /opt/google/chrome/google-chromeAffected if Google Chrome browser is present on the system
-
Determine the installed Chrome versionOpen Chrome, navigate to chrome://version, or run 'google-chrome --version' from command line on Linux/Mac, or check the file properties of chrome.exe on WindowsAffected if A version number is returned that is lower than 149.0.7827.53
-
Compare version against affected rangeCompare the installed version string (e.g., 149.0.7827.52) to the safe version 149.0.7827.53 using semantic version comparisonAffected if The installed version is less than 149.0.7827.53 (e.g., 149.0.7827.52, 148.x.x.x, etc.)
-
Confirm ANGLE graphics component is in useNo manual check needed - ANGLE is used automatically by Chrome for WebGL and graphics rendering. The vulnerability exists in the bundled ANGLE library that ships with Chrome.Affected if Chrome is running and using WebGL or rendering graphics (default behavior)
A user is affected if Google Chrome version is installed and is less than 149.0.7827.53, as the vulnerable ANGLE component is bundled and automatically used for graphics rendering.
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 to obtain the patched ANGLE component; deploy the update organization-wide using standard software distribution mechanisms.
149.0.7827.53
- Open Google Chrome
- Click the three-dot menu in the top-right corner
- Select 'Help' > 'About Google Chrome'
- Chrome will check for updates automatically
- If an update 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 / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10974 — 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-10974 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