External risk intelligence

Skia Memory Corruption in Chrome Allows Remote Code Execution.

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-118340

This vulnerability exists in the Skia graphics library within Google Chrome and requires a user to interact with a crafted HTML page (client-side execution). Because it is a client-side browser component rather than a server-side internet-facing service, appliance, or edge gateway, it is not considered part of a publicly reachable network attack surface in the context of this rubric.

Memory Corruption

Halo Surface Signal: 1 out of 5 — much less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A memory corruption vulnerability in the Skia graphics library used by Google Chrome could allow a remote attacker to execute code outside the browser's sandbox by tricking a user into visiting a malicious webpage.

  • A flaw in Chrome’s graphics library could lead to code execution.
  • It matters if employees use Chrome on suspicious sites.
  • Confirm Chrome usage and user exposure to malicious sites.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into visiting a malicious webpage. This page would contain specially crafted content that targets a weakness in the Skia graphics library within Google Chrome. Successfully triggering this weakness could allow the attacker to run their own code on the user's computer, potentially bypassing security measures.

  • Requires user interaction with a malicious page.
  • Exploits Skia memory corruption.
  • Risk of arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

Memory corruption in Skia could allow an attacker to execute code outside the sandbox when a user visits a malicious HTML page in a vulnerable browser.

  • Arbitrary code execution is at risk.
  • A crafted HTML page can trigger it.
  • Sandbox escape could lead to compromise.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the Skia component of Google Chrome requires user interaction with a malicious HTML page, suggesting that ownership likely falls to teams managing end-user computing, browser security, or application support, rather than infrastructure or network teams. The first practical step is to identify systems running the affected browser version, confirm if they are business-critical, and then coordinate with the relevant application or endpoint owners to plan remediation during the next maintenance window or assess the risk of delaying the update.

  • End-user computing and browser security teams.
  • Confirm browser reachability and business criticality.
  • Plan and execute updates during maintenance windows.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Skia graphics library in Google Chrome?

Skia is an open-source 2D graphics engine that provides the foundation for drawing text, shapes, and images in Google Chrome. It handles the rendering tasks that allow web pages to display visual content correctly on your screen.

What does memory corruption mean in the context of CVE-2026-118340?

This CVE involves a weakness class known as CWE-119, or Improper Restriction of Operations within the Bounds of a Memory Buffer. Essentially, the software fails to safely manage memory, allowing an attacker to manipulate data and potentially run unauthorized code.

How is this vulnerability triggered by an attacker?

An attacker must successfully lure a user into visiting a malicious HTML page. This bug is not triggered by simply having the browser installed or connected to the internet; it specifically requires the browser to process crafted content from a web page.

Is my network infrastructure at risk from CVE-2026-118340?

According to Halo Surface Signal, this is a client-side browser issue, not a server-side service or gateway vulnerability. It is considered very unlikely to affect your internet-facing network infrastructure, as it requires individual user interaction.

How should I prioritize a response to this browser vulnerability?

Focus on your end-user devices. First, identify systems running vulnerable versions of Chrome. Coordinate with endpoint management or browser security teams to schedule the necessary software updates during your next standard maintenance window.

References