dbcve.org
ChromeWeb browser · Google

CVE-2026-10012

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 Skia 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 exists in Skia, the 2D graphics library used by Google Chrome, in versions prior to 148.0.7778.216. An attacker who has already compromised the renderer process can exploit this memory corruption flaw via a specially crafted HTML page to escape the sandbox and execute code in a more privileged context.

MitigationUpdate Google Chrome to version 148.0.7778.216 or later. In enterprise environments, deploy the browser update organization-wide and verify complete coverage across all endpoints.

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. Identify installed Chrome version
    Navigate to chrome://settings/help in the Chrome browser, or run 'google-chrome --version' or 'chrome --version' from command line
    Affected if Version number is below 148.0.7778.216 or 148.0.7778.215 (any version prior to 148.0.7778.216)
  2. Confirm Chrome is the affected browser variant
    Verify the browser is Google Chrome (not Chromium-only builds, Edge, or other Chromium-based browsers that may have different version numbers)
    Affected if Using a Google Chrome variant with version numbering that matches the 148.0.7778.216 threshold
  3. Verify renderer process isolation context
    This vulnerability is a second-stage exploit requiring the renderer process to already be compromised via a separate vulnerability or malicious web content
    Affected if The renderer process has already been compromised by a separate exploit, as this flaw enables sandbox escape from an already-compromised renderer

You are affected if you are running any version of Google Chrome prior to 148.0.7778.216 AND your renderer process has been compromised by a separate exploit, allowing the attacker to escape sandbox isolation through the Skia use-after-free.

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. In enterprise environments, deploy the browser update organization-wide and verify complete coverage across all endpoints.

Recommended fix High confidence

Chrome 148.0.7778.216 or later

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Check the current version number displayed
  3. If the version is below 148.0.7778.216, Chrome will automatically check for updates - click 'Update Google Chrome' if available
  4. Restart Chrome to complete the update
  5. Verify the update was successful by returning to Settings > Help > About Google Chrome and confirming version 148.0.7778.216 or later is installed

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

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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