dbcve.org
ChromeWeb browser · Google

CVE-2026-10981

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
72/100
Remediation priority · Elevated
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
Insufficient validation of untrusted input in Codecs in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted video file. (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 confidence

This is a Same-Origin Policy (SOP) bypass vulnerability in Chrome's video codecs. An attacker who has already compromised the renderer process can exploit insufficient validation of untrusted input in the codec handling to leak cross-origin data by tricking a user into playing a specially crafted video file. The vulnerability allows a confined renderer to escape cross-origin restrictions via malformed media files.

MitigationDeploy Google Chrome version 149.0.7827.53 or later to all affected endpoints. In high-security environments, consider restricting or disabling video playback from untrusted sources until the patch is applied.

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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 installed Google Chrome version
    Navigate to chrome://settings/help or use 'Help > About Google Chrome' to view the installed version number
    Affected if The displayed version is lower than 149.0.7827.53 (for example, 148.x.x.x or earlier)
  2. Verify Chrome is used in the environment
    Confirm Google Chrome browser is installed and in use. Check program files or run 'chrome --version' from command line
    Affected if Chrome is installed and the version from step 1 is less than 149.0.7827.53
  3. Check for signs of renderer process compromise
    Review Chrome's security indicators, look for unexpected extensions, check for unusual network connections from Chrome processes, and examine crash reports for sandbox escapes. Use Process Explorer or similar tools to inspect running Chrome renderer processes for anomalies
    Affected if Signs of renderer compromise are present AND Chrome version is below 149.0.7827.53

A user is affected if they have Google Chrome version below 149.0.7827.53 AND their renderer process has already been compromised by an attacker, allowing them to craft malicious video files that leak cross-origin data through the Codecs component.

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

Deploy Google Chrome version 149.0.7827.53 or later to all affected endpoints. In high-security environments, consider restricting or disabling video playback from untrusted sources until the patch is applied.

Recommended fix High confidence

Chrome 149.0.7827.53 or later

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome to check the current version
  2. If the version is below 149.0.7827.53, Chrome will automatically check for and download the latest update
  3. Restart Chrome to complete the installation of the security update
  4. Alternatively, download the latest stable Chrome version from the official Google Chrome website (google.com/chrome) to ensure the fixed version is installed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10981 — 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-10981 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