dbcve.org
ChromeWeb browser · Google

CVE-2026-9937

HIGH · 8.3 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 148.0.7778.216 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
Use after free in UI in Google Chrome on Windows prior to 148.0.7778.216 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 confidence

Use-after-free vulnerability in the Chrome UI component on Windows (versions prior to 148.0.7778.216) allows a remote attacker who has already compromised the renderer process to potentially escape the browser sandbox via a crafted HTML page.

MitigationUpgrade Google Chrome to version 148.0.7778.216 or later to patch the 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:< 148.0.7778.216

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. Verify the operating system is Windows
    Check if the system is running Windows. On the command line, run 'systeminfo | findstr /B /C:"OS Name"' or check system properties.
    Affected if The system is not running Windows - this vulnerability only affects Chrome on Windows systems.
  2. Identify the installed Google Chrome version on Windows
    Open Chrome and navigate to chrome://version, or run 'google-chrome --version' or 'chrome --version' from command line, or check the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome for the Version value.
    Affected if Unable to determine the installed Chrome version - cannot assess vulnerability status.
  3. Compare the installed version against the fixed version
    Compare the version found in step 2 to 148.0.7778.216. Note that Chrome versions follow semantic versioning, so compare each component numerically.
    Affected if The installed version is less than 148.0.7778.216 (for example, 148.0.7778.215, 148.0.7777.100, or any earlier version). This indicates the system is running a vulnerable version.
  4. Confirm Chrome is actively used on the Windows system
    Check if Google Chrome is installed and in use. Look for Chrome installation directory (typically C:\Program Files\Google\Chrome\Application\) or check for chrome.exe process.
    Affected if Chrome is not installed or not in use on the Windows system - the vulnerability cannot be exploited in this environment.

The system is affected if it is running Google Chrome on Windows with a version lower than 148.0.7778.216 and the attacker has already compromised the renderer process.

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 148.0.7778.216 or later
Fixed in 148.0.7778.216
Interim mitigation

Upgrade Google Chrome to version 148.0.7778.216 or later to patch the vulnerability.

Recommended fix High confidence

Chrome 148.0.7778.216

  1. Open Google Chrome on your Windows machine
  2. Click on the three-dot menu icon in the top-right corner
  3. Select "Help" from the dropdown menu
  4. Click on "About Google Chrome"
  5. Chrome will automatically check for and download updates
  6. Wait for the update to complete (version 148.0.7778.216 or later)
  7. Click "Relaunch" to restart Chrome and apply 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
  • 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-9937 — 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-9937 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