dbcve.org
ChromeWeb browser · Google

CVE-2026-9883

HIGH · 8.8 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 →
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 Base in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to execute arbitrary code via a crafted HTML page. (Chromium security severity: Critical)

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 exists in the Base component of Google Chrome versions prior to 148.0.7778.216. This memory corruption flaw allows a remote attacker to execute arbitrary code by tricking users into visiting a specially crafted HTML page that triggers the vulnerability when the browser parses and processes the malicious content.

MitigationUpdate Google Chrome to version 148.0.7778.216 or later to patch the vulnerability. Organizations should deploy the browser update across all affected endpoints and verify successful installation.

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
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. Determine installed Chrome version
    Open Google Chrome, click the three-dot menu in the top-right corner, then select Help > About Google Chrome. Alternatively, navigate to chrome://settings/help in the address bar. Note the version number displayed on the page.
    Affected if The version shown is lower than 148.0.7778.216 or 148.0.7778.215, indicating the browser is vulnerable to the use-after-free flaw in the Base component.
  2. Verify the exact version number
    Compare your installed version number against the affected ranges. Chrome versions follow the format major.minor.build.patch (for example, 148.0.7778.100). Any version below 148.0.7778.216 is considered affected.
    Affected if Your installed version starts with 148 but has a build/patch number below 7778.216, or it is any version prior to the 148 release branch.
  3. Confirm Google Chrome is the browser
    Ensure the browser being used is Google Chrome specifically, not a Chromium-based alternative like Microsoft Edge, Brave, or Opera. Check the browser name in the title bar or under Help > About.
    Affected if The browser is Google Chrome with a version below 148.0.7778.216. Other Chromium-based browsers may have different version numbers and patch timelines.

Your environment is affected if Google Chrome is installed with any version earlier than 148.0.7778.216.

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 to patch the vulnerability. Organizations should deploy the browser update across all affected endpoints and verify successful installation.

Recommended fix High confidence

Chrome 148.0.7778.216 or later (stable channel)

  1. Open Google Chrome
  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 and install updates
  6. Restart Chrome if an update was installed

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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