ChromeWeb browser · Google
CVE-2026-10924
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 Chromecast in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process 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 confidenceInteger overflow vulnerability in Chromecast's Google Chrome component (pre-149.0.7827.53) allows a remote attacker who has already compromised the renderer process to potentially escape the sandbox via 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
< 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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.
-
Verify Google Chrome is installedCheck for Google Chrome browser on the system - look for Chrome executable (chrome.exe on Windows, Google Chrome.app on macOS, or google-chrome on Linux) in standard installation directories or via system application listingAffected if Google Chrome is present on the system
-
Find installed Chrome version (Windows)Open Chrome and navigate to chrome://version, or right-click the Chrome shortcut and select Properties to view the version in the Target fieldAffected if The displayed version is earlier than 149.0.7827.53
-
Find installed Chrome version (macOS)Open Chrome, click Chrome menu, then select About Google Chrome to display the version numberAffected if The displayed version is earlier than 149.0.7827.53
-
Find installed Chrome version (Linux)Run 'google-chrome --version' or 'google-chrome-stable --version' from command lineAffected if The displayed version is earlier than 149.0.7827.53
The system is affected if Google Chrome is installed with any version prior to 149.0.7827.53, since the integer overflow in the Chromecast component can be exploited when a crafted HTML page is loaded after prior renderer compromise.
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 on Chromecast devices to version 149.0.7827.53 or later; for embedded Chromecast firmware, apply any available Google firmware updates that include the Chrome security patch.
Chrome 149.0.7827.53 or later (stable release)
- Open Chrome and navigate to Settings > About Chrome to check current version
- Download Chrome version 149.0.7827.53 or later from the official Chrome download page (chrome.com)
- Install the updated version, or restart Chrome to allow automatic updates to apply
- Verify the version after update by returning to Settings > About Chrome
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10924 — 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-10924 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