ChromeWeb browser · Google
CVE-2026-15766
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 · uneditedUninitialized Use in Skia in Google Chrome prior to 150.0.7871.125 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 confidenceUninitialized use vulnerability in Skia (Google's graphics library) in Google Chrome allows a remote attacker to read potentially sensitive information from process memory via a crafted HTML page. The vulnerability stems from the renderer reading uninitialized memory in the graphics pipeline and exposing it, enabling information disclosure.
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
< 150.0.7871.125CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' / 'chrome --version' in terminalAffected if Version displayed is earlier than 150.0.7871.125 (e.g., 150.0.7871.100, 149.x.x.x, etc.)
-
Verify Chrome is actively used for web renderingConfirm Chrome browser is used to render HTML content from untrusted sourcesAffected if Users browse web pages with Chrome, as the vulnerability triggers when rendering a crafted HTML page in the renderer process
-
Confirm Skia graphics component is enabledSkia is built into Chrome's rendering pipeline by default; verify Chrome is not running with special flags that disable GPU/rendering featuresAffected if Chrome runs with standard rendering pipeline (default configuration) - the vulnerability exists in the graphics library used for all canvas/Skia drawing operations
You are affected if Chrome version is lower than 150.0.7871.125 and the browser is used to render web content, as the flaw allows the renderer to read uninitialized memory in the Skia graphics library via a crafted HTML page.
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 · scoped150.0.7871.125
Update Google Chrome to version 150.0.7871.125 or later to obtain the security patch. As a defense-in-depth measure, disable JavaScript in untrusted contexts to reduce attack surface.
Chrome 150.0.7871.125 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Verify the current version number
- If the version is below 150.0.7871.125, Chrome will automatically check for and apply updates
- Restart Chrome after the update completes
- Confirm the version has updated to 150.0.7871.125 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15766 — 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-15766 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