dbcve.org
ChromeWeb browser · Google

CVE-2026-10949

HIGH · 8.3 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Heap buffer overflow in Video 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 · moderate confidence

Heap buffer overflow vulnerability in Google Chrome's Video component prior to version 149.0.7827.53 allows a remote attacker with an already compromised renderer process to potentially escape the sandbox by tricking the user into visiting a crafted HTML page.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later to patch the vulnerability; ensure automatic updates are enabled for endpoints.

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
Affected:< 149.0.7827.53

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Google Chrome version
    Open Chrome and navigate to chrome://version, or click Help > About Google Chrome. Note the version number displayed.
    Affected if The displayed version is below 149.0.7827.53
  2. Verify Chromium-based browser versions
    If you use other Chromium-based browsers such as Microsoft Edge, Brave, or Opera, check each one's version via their respective About menus or version pages (edge://version, brave://version, etc.).
    Affected if Any Chromium-based browser on the system is below its corresponding patched version for this vulnerability.
  3. Confirm video processing feature usage
    This vulnerability affects Chrome's video processing component. Determine if users routinely handle video files or visit untrusted web pages that could serve crafted video content.
    Affected if Users process video content or browse the web with Chrome, and the browser version is vulnerable.
  4. Check for renderer process compromise indicators
    Review Chrome's security logs or enterprise endpoint detection tools for signs of renderer process compromise, as this vulnerability requires an already-compromised renderer.
    Affected if Evidence exists of renderer process compromise alongside a vulnerable Chrome version.

You are affected if Google Chrome or any Chromium-based browser installed is version 149.0.7827.53 or lower, and users interact with web content or video files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 149.0.7827.53 or later
Fixed in 149.0.7827.53
Interim mitigation

Update Google Chrome to version 149.0.7827.53 or later to patch the vulnerability; ensure automatic updates are enabled for endpoints.

Recommended fix High confidence

149.0.7827.53 or later (Chrome stable channel)

  1. 1. Open Google Chrome and navigate to Help > About Google Chrome to check the current version
  2. 2. If the version is earlier than 149.0.7827.53, Chrome will automatically check for and offer an update
  3. 3. Click 'Update Google Chrome' if prompted, or manually download the latest Chrome version from the official Google Chrome download page (chrome.google.com)
  4. 4. Restart Chrome after the update completes to apply the fix
  5. 5. Verify the version is now 149.0.7827.53 or later via Help > About Google Chrome
Caveat Chrome updates typically do not introduce breaking changes for end users; ensure all extensions are compatible with the new version

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
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10949 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10949 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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