External risk intelligence

Google Chrome Forms Out of Bounds Write Allows Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-113300

The vulnerability exists in the Forms component of the Google Chrome web browser. While web browsers are internet-facing applications, this specific exploit requires a user to navigate to a crafted HTML page. It is not an infrastructure service, gateway, or management portal that is publicly accessible by design, making widespread unprompted internet exposure less common than edge services.

Out-of-bounds Write

Halo Surface Signal: 3 out of 5 — possibly public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability identified in Google Chrome's Forms feature. While not directly exploitable without user interaction, it presents a potential for attackers to execute code outside the browser's safe environment if a user visits a malicious webpage. The overall severity is rated low.

  • Flaw in browser forms may allow code execution.
  • Potential for hidden malicious code if users visit bad sites.
  • Confirm relevance and assess exposure of affected users.

Attack Path

How an attacker could exploit the issue

An attacker can trick a user into visiting a malicious webpage, which then targets a vulnerability in Chrome's Forms component. This could allow the attacker to execute code on the user's device, potentially escaping the browser's security sandbox.

  • Requires user interaction with a malicious site.
  • Triggered by navigating to a crafted HTML page.
  • Risk of arbitrary code execution outside the sandbox.

Live Threat

Current exploitation, exposure, and threat context

A remote attacker could exploit a vulnerability in Google Chrome's Forms component by tricking a user into visiting a malicious HTML page. This could allow the attacker to execute code outside the browser's security sandbox, potentially impacting the user's device.

  • User data and system integrity at risk.
  • Via a crafted HTML page interaction.
  • Potential for arbitrary code execution.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Google Chrome's Forms component requires user interaction via a crafted HTML page, suggesting that initial triage should focus on identifying user-facing systems and understanding exposure through user activity. Application owners and security teams should collaborate to assess risk, with vendor management playing a role if managed deployments are affected. The practical first step involves locating all instances of the affected browser, determining business criticality, identifying accountable owners, and then planning remediation based on a risk assessment.

  • Identify affected users and systems.
  • Verify user exposure and criticality.
  • Coordinate vendor updates and user guidance.

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 and how does its Forms component work?

Google Chrome is a widely used web browser that renders HTML content to display websites. The Forms component is a specific part of the browser's engine responsible for processing user-input fields, such as text boxes, checkboxes, and buttons, found on web pages. It interprets the code sent by websites to ensure these interactive elements function correctly when you engage with them.

What does CWE-787 mean regarding CVE-2026-113300?

CWE-787 refers to an 'Out-of-bounds Write' vulnerability. In the context of this CVE, it means the browser's Forms component fails to properly check memory boundaries when processing data. This weakness allows an attacker to write information into parts of the computer's memory that should be restricted. By exploiting this, a malicious actor could potentially run unauthorized code, effectively breaking out of the security restrictions the browser uses to keep your device safe.

How is this vulnerability triggered?

This flaw is triggered when a user navigates to a specifically crafted HTML page designed to exploit the memory error in the Forms component. The vulnerability does not activate simply by having the browser installed or running in the background; it requires the active step of visiting a malicious web page. Normal browsing on legitimate, trusted websites does not trigger this specific issue.

Who should care about CVE-2026-113300 according to Halo Surface Signal?

Anyone running Google Chrome versions prior to 156.0.8078.47 should care. Halo Surface Signal notes that while the browser itself is internet-facing, this vulnerability is not an infrastructure service exposed by design. Instead, it relies on tricking a user into navigating to a malicious site. Therefore, environments where users frequently browse diverse or unverified content face a higher relevance, as the threat depends on human interaction rather than direct network-level attacks.

How do I address this Chrome vulnerability?

The most effective first step is to verify the version of Google Chrome installed across your systems. Identify which devices are running outdated versions and prioritize updating them to the latest release provided by the vendor. Since this issue requires user interaction, informing users to remain cautious of suspicious links and ensuring automated update policies are active are critical parts of managing this risk.

References