ChromeWeb browser · Google
CVE-2026-9893
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 · uneditedUse 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: 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 confidenceUse-after-free vulnerability in Skia graphics library in Google Chrome prior to version 148.0.7778.216. A remote attacker with a compromised renderer process could exploit this to potentially escape the sandbox via a crafted HTML page.
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
< 148.0.7778.216CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Google Chrome is installedOn Windows: Look for chrome.exe in Program Files or %LOCALAPPDATA%\Google\Chrome\Application. On macOS: Check /Applications/Google Chrome.app. On Linux: Check /usr/bin/google-chrome or /opt/google/chrome/Affected if Google Chrome browser is present on the system
-
Determine installed Chrome versionOpen Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' from command line. The version displays as a four-part number such as 147.0.6134.115Affected if Chrome is installed but version cannot be determined
-
Compare version against affected rangeCompare the installed version number to 148.0.7778.216. Any version less than 148.0.7778.216 (including 147.x.x.x, 146.x.x.x, older) falls within the affected rangeAffected if Installed version is numerically less than 148.0.7778.216
-
Confirm Chrome update channel statusIn Chrome, go to chrome://settings and check under 'About Chrome' to see if updates are enabled and what version is reported as currentAffected if Chrome reports being out of date or automatic updates are disabled
The system is affected if Google Chrome is installed with a version lower than 148.0.7778.216, as this version range contains the vulnerable Skia graphics code in the renderer process.
Generated from the published advisory. Verify against your own configuration.
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 · scoped148.0.7778.216
Update Google Chrome to version 148.0.7778.216 or later. Organizations should deploy the update through their patch management systems and verify completion across endpoints.
Chrome version 148.0.7778.216 or later
- Open Google Chrome
- Click the three-dot menu in the top-right corner
- Select 'Help' > 'About Google Chrome'
- Chrome will check for updates and display the current version
- If a newer version is available, click 'Update Google Chrome'
- Restart Chrome to complete the update
- Verify the version is 148.0.7778.216 or later by returning to Help > About Google 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
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9893 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9893 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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