dbcve.org
ChromeWeb browser · Google

CVE-2026-11050

HIGH · 8.8 CVSS v3.1 Published 2026-06-04
Fix available
A fix is available. Upgrade to 149.0.7827.53 or later.
See remediation →
95/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
Use after free in V8 in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: Medium)

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

Use-after-free vulnerability in Chrome's V8 JavaScript engine allows a remote attacker to execute arbitrary code inside the sandbox through a malicious HTML page. The vulnerability exists in versions prior to 149.0.7827.53.

MitigationUpdate Google Chrome to version 149.0.7827.53 or later to patch the V8 use-after-free vulnerability.

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

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

  1. Check installed Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or run 'google-chrome --version' from command line
    Affected if The displayed version is lower than 149.0.7827.53
  2. Verify V8 JavaScript engine is in use
    Open any webpage in Chrome, then navigate to chrome://inspect to confirm JavaScript engine details, or check that JavaScript executes normally in the browser
    Affected if V8 is the JavaScript engine used by Chrome and is always active when browsing with JavaScript enabled
  3. Confirm browser is used for untrusted content
    Review whether the Chrome installation is used to browse untrusted or external websites, or if it renders HTML content from untrusted sources
    Affected if The browser is used to visit potentially malicious webpages that could contain the crafted HTML trigger
  4. Check sandbox status (optional context)
    Navigate to chrome://sandbox in the browser to see sandbox status, or review Chrome policy settings related to sandboxing
    Affected if The sandbox is disabled, which would affect the overall security posture though the vulnerability executes inside a sandbox by default

You are affected if your Chrome version is lower than 149.0.7827.53 and you use the browser to access untrusted web content that could contain the crafted HTML page.

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 V8 use-after-free vulnerability.

Recommended fix High confidence

Chrome version 149.0.7827.53 or later

  1. Open Google Chrome browser
  2. Click the three-dot menu icon in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. Chrome will automatically check for updates and display the current version
  6. If a version lower than 149.0.7827.53 is shown, click 'Update Google Chrome' to download and install the fix
  7. Restart the browser completely to apply the update
  8. Verify the version by returning to About Google Chrome and confirming it shows 149.0.7827.53 or later
Caveat Chrome updates typically have minimal breaking changes; however, some legacy web apps may experience compatibility issues with the newer V8 engine

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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