dbcve.org
ChromeWeb browser · Google

CVE-2026-9905

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 Accessibility 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 Google Chrome's Accessibility component on Windows (versions prior to 148.0.7778.216). A remote attacker with a compromised renderer process can exploit this to potentially escape the sandbox via a crafted HTML page.

MitigationUpgrade Google Chrome to version 148.0.7778.216 or later. In enterprise environments, deploy the update via centralized software distribution mechanisms and verify successful patching across all Windows clients.

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 Google Chrome is installed on Windows
    Check for Chrome in the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome or look for chrome.exe in common installation paths like C:\Program Files\Google\Chrome\Application\
    Affected if Google Chrome browser is found on the system
  2. Determine the installed Chrome version
    Open chrome://version in the Chrome browser address bar and note the version number displayed, or check the Version value in the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome
    Affected if The version shown is less than 148.0.7778.216
  3. Confirm the operating system is Windows
    Verify the affected system is running Windows - check system properties or run 'winver' command
    Affected if The system is running Windows (the vulnerability specifically affects Windows versions)
  4. Understand the attack prerequisites
    Note that this vulnerability requires an attacker to have already compromised the Chrome renderer process - this is not an initial infection vector but a privilege escalation method
    Affected if The system has already been compromised at the renderer process level, making this a secondary exploit

If Google Chrome version 148.0.7778.216 or later is installed on Windows, the environment is not affected by this CVE; any version below 148.0.7778.216 on Windows is within the affected range.

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. In enterprise environments, deploy the update via centralized software distribution mechanisms and verify successful patching across all Windows clients.

Recommended fix High confidence

148.0.7778.216

  1. Open Google Chrome on Windows
  2. Click the three-dot menu in the top-right corner
  3. Select 'Help' and then 'About Google Chrome'
  4. The current version will be displayed under 'Google Chrome'
  5. If the version shown is below 148.0.7778.216, Chrome will automatically check for and install updates
  6. Restart Chrome after the update completes
  7. Verify the version is now 148.0.7778.216 or later by returning to Help > About Google Chrome

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

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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