dbcve.org
ChromeWeb browser · Google

CVE-2026-9924

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
Heap buffer overflow in ANGLE 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

A heap buffer overflow vulnerability exists in the ANGLE graphics translation layer within Google Chrome on Windows versions prior to 148.0.7778.216. An attacker who has already compromised the renderer process can exploit this flaw via a crafted HTML page to potentially escape the sandbox and gain elevated privileges.

MitigationUpdate Google Chrome to version 148.0.7778.216 or later on all affected Windows systems to remediate this 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 Google Chrome is installed on Windows
    Open Control Panel > Programs and Features, or run 'Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome"' in PowerShell to check for Chrome installation
    Affected if Google Chrome is present on the system
  2. Determine the installed Google Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or run '"C:\Program Files\Google\Chrome\Application\chrome.exe" --version' via command prompt
    Affected if The displayed version is lower than 148.0.7778.216
  3. Compare version against the affected range
    Compare your installed version number to 148.0.7778.216 using standard version comparison
    Affected if Your installed version is less than 148.0.7778.216 (for example, 148.0.7778.200 or any earlier version)
  4. Confirm the vulnerability context requires a compromised renderer
    Understand that this flaw is exploitable only after an attacker has already compromised the Chrome renderer process
    Affected if A compromised renderer process exists in your environment alongside a vulnerable Chrome version

You are affected if Google Chrome version 148.0.7778.216 or earlier is installed on your Windows system and a renderer process compromise has occurred or could occur.

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

Update Google Chrome to version 148.0.7778.216 or later on all affected Windows systems to remediate this vulnerability.

Recommended fix Moderate confidence

Chrome version 148.0.7778.216 or later (stable release)

  1. 1. Open Google Chrome and navigate to Settings (three dots menu > Settings)
  2. 2. Click on 'About Chrome' in the left sidebar
  3. 3. Chrome will automatically check for updates and display the current version
  4. 4. If an update is available, click 'Update Google Chrome'
  5. 5. Restart Chrome to complete the installation
  6. 6. Verify the version is 148.0.7778.216 or later by returning to 'About Chrome'

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-9924 — 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-9924 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