Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Integer overflow in Skia in Google Chrome

IdentifiersCVE-2026-8510CWE-190

CVE-2026-8510 is a critical integer overflow vulnerability in the Skia graphics component of Google Chrome on Windows prior to version 148.0.7778.168. According to the provided content, a remote attacker who has already compromised the renderer process can trigger the flaw via a crafted HTML page, leading to an out-of-bounds memory write. The issue is therefore a memory-corruption bug rooted in improper handling of integer arithmetic in Skia, where an overflow can cause incorrect size or bounds calculations and subsequently permit a write outside the intended memory region.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can result in out-of-bounds memory corruption within Chrome. Based on the provided content, this gives an attacker who has already achieved renderer-process compromise a path to further exploit the browser, potentially enabling arbitrary code execution, sandbox escape facilitation, browser compromise, or compromise of the underlying host, depending on exploit chaining and runtime conditions. Google rated the issue Critical.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by accelerating Chrome update deployment, restricting use of untrusted web content, and applying enterprise controls that limit renderer compromise opportunities. Because the provided content states exploitation requires prior renderer-process compromise, hardening measures that reduce initial renderer exploitation and enforcing rapid browser restarts after update deployment may lower risk. However, no mitigation equivalent to patching is provided in the source content.

Remediation

Patch, then assume compromise.

Update Google Chrome on Windows to version 148.0.7778.168 or later. The provided content indicates that Google released a Chrome security update addressing this vulnerability as part of a broader set of fixes. Applying the vendor update is the primary remediation.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.