dbcve.org
ChromeWeb browser · Google

CVE-2026-9997

HIGH · 8.3 CVSS v3.1 Published 2026-05-28
Fix available
A fix is available. Upgrade to 148.0.7778.215 / 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 Input in Google Chrome 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 use-after-free vulnerability in Chrome's Input component (versions prior to 148.0.7778.216) allows a remote attacker who has compromised the renderer process to potentially escape the sandbox. The flaw involves improper memory management where a pointer to a freed object is reused after deallocation.

MitigationUpdate Google Chrome to version 148.0.7778.216 or later. Organizations should ensure browsers are updated via enterprise deployment or automatic updates, and consider additional sandboxing or isolation for high-risk users.

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

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 Chrome is installed
    Check for Chrome installation by looking for the executable. On Windows, check C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, check /usr/bin/google-chrome or /opt/google/chrome/google-chrome.
    Affected if Chrome is not installed on the system
  2. Determine installed Chrome version
    Open Chrome, navigate to chrome://settings/help, or from command line run 'chrome --version' (Windows) or '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' (macOS) or 'google-chrome --version' (Linux).
    Affected if Unable to retrieve version information from Chrome installation
  3. Compare version against affected range
    Compare the installed version number to 148.0.7778.216 (and 148.0.7778.215). Note the full version string including the three-digit component (e.g., 148.0.7778.100).
    Affected if Installed version is less than 148.0.7778.216 or less than 148.0.7778.215 (depending on the specific channel version reported)
  4. Confirm vulnerability context applies
    Review whether the browser processes untrusted HTML content from the internet, as exploitation requires a compromised renderer process and a crafted HTML page.
    Affected if Chrome processes untrusted web content and version is below 148.0.7778.216

The environment is affected if Google Chrome is installed with a version lower than 148.0.7778.216 and the browser processes untrusted HTML content.

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.215 / 148.0.7778.216 or later
Fixed in 148.0.7778.215148.0.7778.216
Interim mitigation

Update Google Chrome to version 148.0.7778.216 or later. Organizations should ensure browsers are updated via enterprise deployment or automatic updates, and consider additional sandboxing or isolation for high-risk users.

Recommended fix High confidence

Chrome 148.0.7778.216 or later

  1. Open Chrome and navigate to Menu > Help > About Google Chrome
  2. Verify the current version number displayed
  3. If the version is below 148.0.7778.216, Chrome will automatically check for updates
  4. Click 'Update Google Chrome' if an update is available
  5. Restart Chrome to complete the installation
  6. Alternatively, download the latest stable Chrome from the official website (google.com/chrome) and run the installer
Caveat Minimal for end users; ensure your operating system meets Chrome 148's requirements (typically Windows 7+, macOS 10.12+, or Linux)

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
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
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,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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