External risk intelligence

Chrome Video Buffer Overflow Vulnerability Allows Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-95318

The vulnerability exists in a widely deployed web browser. While it requires a user to navigate to a crafted HTML page, web browsers are primary tools for accessing the public internet, and this surface is routinely exposed to external content as a standard part of its design and deployment.

Buffer Overflow

Google Chrome

before 154.0.8037.57

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A buffer overflow vulnerability in Google Chrome could allow an unauthenticated attacker to execute code remotely via a malicious webpage, potentially impacting user data and system integrity.

A bug in Chrome could let attackers run code.
Affects widely used web browsing technology.
Confirm relevance; understand potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker can trick a user into visiting a malicious HTML page, which triggers a buffer overflow vulnerability in Google Chrome's video component. This vulnerability could allow the attacker to execute arbitrary code outside of the browser's security sandbox.

Requires user interaction with a crafted page.
Vulnerability in video processing.
Potential for arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

A buffer overflow vulnerability in Google Chrome could allow a remote attacker to execute arbitrary code outside the sandbox when a user visits a maliciously crafted HTML page. This could impact the integrity and confidentiality of the system and user data.

System and user data at risk.
Exposure via crafted HTML pages.
Potential for arbitrary code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Google Chrome impacts users who encounter malicious HTML pages. The primary responsibility for managing this risk likely falls to IT infrastructure and security teams who oversee browser deployments and network security, in coordination with application owners who may dictate browser standards. The first practical step is to identify all Chrome instances, confirm their reachability and criticality, and then prioritize patching or other mitigation strategies based on potential exposure.

Own the issue: Infrastructure and security teams.
Verify first: Identify all Chrome instances.
Action: Plan and execute updates.

Supplementary metadata

CVSS vector

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.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Google Chrome in the context of this CVE?

Google Chrome is a widely used web browser that renders web content, including complex media like video. It includes a security sandbox designed to isolate web page processing from your underlying operating system. This vulnerability specifically affects the browser's video component, which is responsible for decoding and displaying video streams encountered during web browsing.

What does CWE-122 mean for CVE-2026-95318?

CWE-122 refers to a heap-based buffer overflow. In plain terms, this means the video processing component tries to store more data in a specific memory area than it can handle. Because it overflows its designated space, it can corrupt adjacent memory. In this CVE, that corruption potentially allows an attacker to bypass the browser's sandbox and run unauthorized code.

How is this Chrome buffer overflow triggered?

An attacker must trick a user into visiting a specifically crafted HTML page that contains malicious video data. Simply having the browser installed is not enough to trigger the bug. The vulnerability is not activated by static content or standard, safe web browsing; it requires the browser to actively process the malicious code embedded within the crafted page.

Why should I care about CVE-2026-95318?

According to Halo Surface Signal, this vulnerability is a high priority because Google Chrome is a primary tool for accessing the internet. Since the browser is constantly exposed to external, untrusted content, the ability for an attacker to achieve remote code execution outside the sandbox makes this a significant risk for any system where users browse the web.

What is the first step to address this Chrome vulnerability?

The most effective first step is to verify the version of Chrome running across your environment. Because this vulnerability is resolved in version 154.0.8037.57 and later, you should inventory your current installations and prioritize updating any instances still running older, affected versions to the latest stable release provided by Google.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.