CVE-2026-113158 Google CVE debrief

Who should care

Chrome users and administrators should assess exposure and prioritize remediation due to the potential for code execution within the sandbox. This vulnerability is particularly relevant for environments where Chrome is used extensively, such as in business or educational settings. IT and security teams responsible for managing Chrome deployments should review their inventory of Chrome installations and ensure they are updated to version 156.0.8078.47 or later.

Why it matters

CVE-2026-113158 is a use-after-free vulnerability in Google Chrome's Streaming component that could allow remote attackers to execute arbitrary code within the sandbox. Chrome users and administrators should assess exposure and prioritize remediation.

• Potential for arbitrary code execution within the sandbox
• Requires immediate attention from Chrome administrators
• Necessitates review and update of Chrome installations
• May impact environments with extensive Chrome usage

Technical summary

The CVE-2026-113158 vulnerability involves a use-after-free issue in the Streaming component of Google Chrome. This type of vulnerability occurs when a program attempts to access memory that has already been freed or deleted. In this case, an attacker could potentially exploit this vulnerability by crafting a malicious HTML page that, when opened in a vulnerable version of Chrome, could allow for arbitrary code execution within the sandbox environment. The Chromium security team has classified this issue as Medium severity.

Defensive priority

High

Recommended defensive actions

• Upgrade Google Chrome to version 156.0.8078.47 or later
• Review and update inventory of Chrome installations to ensure compliance
• Monitor Chrome release notes and security advisories for future updates
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and source item provide details on the vulnerability, including its existence in Chrome versions prior to 156.0.8078.47 and a reference to a Chromium security severity classification as Medium.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.