External risk intelligence

Chrome DevTools Off-by-One Memory Read Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-79148

This vulnerability requires the installation and use of a crafted, malicious Chrome extension and involves social engineering to achieve impact within the browser's sandbox. It is not an internet-facing service or protocol that is directly reachable by a remote attacker.

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

This advisory concerns a vulnerability in Google Chrome that could allow a specially crafted extension, combined with social engineering, to potentially read memory within the browser's sandbox. While the technical severity is rated low, the attack vector is network-accessible and could lead to information disclosure if exploited.

  • Bug could let extensions read browser memory.
  • Social engineering needed for potential data exposure.
  • Confirm if extensions access sensitive data.

Attack Path

How an attacker could exploit the issue

An attacker could trick a user into installing a malicious Chrome extension, which, when used, could read sensitive information from the browser's memory. This attack leverages a flaw in Chrome's developer tools that allows an attacker to potentially access data within the browser's isolated sandbox.

  • No authentication required to start.
  • User installs malicious extension.
  • Potential to read sensitive memory.

Live Threat

Current exploitation, exposure, and threat context

A remote attacker could potentially read memory from within the Chrome sandbox by tricking a user into installing and interacting with a malicious Chrome extension. This could expose sensitive information that the browser has access to.

  • Memory within the browser sandbox.
  • Via a malicious Chrome extension and social engineering.
  • Sensitive information exposure.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Chrome's DevTools, while rated critical, requires user interaction through social engineering and a malicious extension, making its real-world exploit less direct. The first practical move is to identify Chrome installations, assess their reachability and criticality, and then coordinate with application owners and potentially the Chrome enterprise support team for remediation planning, considering the low severity of the underlying bug.

  • Application owners should prioritize addressing this.
  • Verify Chrome extension management policies.
  • Plan for Chrome browser updates.

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 Google Chrome DevTools?

Google Chrome DevTools is a built-in suite of web developer instruments included with the browser. It allows developers to debug, test, and inspect the structure of web pages and running scripts. While typically used for web development, this vulnerability concerns a flaw within that specific component's internal logic.

What does an off-by-one error mean for CVE-2026-79148?

This is a CWE-193 weakness, which occurs when a program makes a small miscalculation in indexing, such as reading one position past the end of a memory buffer. In this CVE, that tiny error allows the DevTools component to access information it should not be able to see, potentially leaking data from the browser's internal memory.

How does an attacker trigger this vulnerability?

The flaw is not triggered simply by visiting a website. It requires a two-step process: an attacker must first convince a user to install a specific, malicious Chrome extension, and the user must then interact with that extension. Without the installation of this harmful add-on, the browser's sandbox remains protected against this specific bug.

Is my system at risk according to Halo Surface Signal?

Halo Surface Signal notes that this is very unlikely to pose an immediate risk because it is not an internet-facing service or protocol. Because the attack requires active user participation to install malicious software, it is not directly reachable by a remote attacker over the network without that social engineering step.

What should I do to address this Chrome vulnerability?

The most effective response is to update your browser to version 152.0.7977.65 or later, which contains the fix. Additionally, review your organization's browser extension policies to ensure that only approved, trusted extensions are allowed to be installed by users, as this mitigates the primary trigger for this memory access issue.

References