dbcve.org
ChromeWeb browser · Google

CVE-2026-9981

MEDIUM · 6.5 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 →
72/100
Remediation priority · Elevated
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
Inappropriate implementation in Skia in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to obtain potentially sensitive information from process memory 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

This is an information disclosure vulnerability in Skia, Google's graphics rendering library used by Chrome. A remote attacker can craft a malicious HTML page that triggers 'inappropriate implementation' in Skia's rendering logic, allowing the attacker to read sensitive data from the browser process memory (potentially including cookies, session tokens, or other sensitive information).

MitigationUpdate Google Chrome to version 148.0.7778.216 or later. Organizations should ensure endpoint management policies push browser updates and verify patch compliance.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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. Identify Chrome installation path and version
    Open Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help. Alternatively, run 'google-chrome --version' from command line on Linux, or check Program Files/Google/Chrome/Application/ folder for version on Windows.
    Affected if The displayed version number is lower than 148.0.7778.216 (or 148.0.7778.215, depending on the specific branch).
  2. Determine if Skia rendering is in use
    Skia is the default 2D rendering engine in Chrome and cannot be easily disabled. No configuration change is needed to be vulnerable; simply using Chrome with the default rendering pipeline exposes the attack surface.
    Affected if Chrome is running with default settings (Skia is always enabled in modern Chrome versions).
  3. Confirm Chrome is exposed to remote content
    Check whether Chrome is used to browse the web or render untrusted HTML content. This vulnerability is triggered by a remote attacker serving a crafted HTML page, so any Chrome instance that can access websites is potentially affected.
    Affected if The browser has network access or is used to render content from untrusted sources.

You are affected if your installed Chrome version is below 148.0.7778.216 and you use the browser to access web content, as the Skia vulnerability requires no special configuration to be exploitable.

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 endpoint management policies push browser updates and verify patch compliance.

Recommended fix Moderate confidence

Chrome 148.0.7778.216 or later

  1. Open Google Chrome
  2. Click the three-dot menu in the top-right corner
  3. Select 'Help' > 'About Google Chrome'
  4. Chrome will check for updates and automatically download version 148.0.7778.216 or later
  5. Click 'Relaunch' to apply the update
  6. Verify the update was successful by returning to Help > About Chrome and confirming the version is 148.0.7778.216 or higher

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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