CVE-2026-113136 Google CVE debrief

Who should care

Defenders and IT administrators responsible for Google Chrome deployments, especially in environments with remote access or exposure to untrusted input, should assess exposure and apply patches.

Why it matters

CVE-2026-113136 is a Medium-severity memory corruption vulnerability in Google Chrome's DevTools that allows remote attackers to execute arbitrary code within the sandbox. Defenders should assess exposure, apply patches, and monitor for potential exploitation attempts.

• Remote code execution within the sandbox requires verification of Chrome version and exposure.
• Potential for crafted HTML pages to trigger vulnerability; defenders should monitor for suspicious activity.
• Patching Chrome to version 156.0.8078.47 or later is recommended to mitigate this vulnerability.
• Incident response plans should be reviewed to address potential sandbox escapes.

Technical summary

CVE-2026-113136 is a memory corruption vulnerability in Google Chrome's DevTools. It allows remote attackers to execute arbitrary code within the sandbox via a crafted HTML page. The vulnerability was reported with a Medium severity level by the Chromium security team and affects Chrome versions prior to 156.0.8078.47. The issue arises from improper handling of certain HTML pages, leading to memory corruption. To mitigate this vulnerability, defenders should prioritize assessing exposure and applying patches for Google Chrome users, especially in environments where remote access or untrusted input is common.

Defensive priority

Defenders should prioritize assessing exposure and applying patches for Google Chrome users, especially in environments where remote access or untrusted input is common.

Recommended defensive actions

• Assess exposure for Google Chrome users in your environment, especially those with remote access or exposure to untrusted input.
• Verify and apply the patch to update Google Chrome to version 156.0.8078.47 or later.
• Monitor for potential exploitation attempts targeting this vulnerability.
• Review and update incident response plans to address potential sandbox escapes.
• 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.

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 the potential for arbitrary code execution within the sandbox.

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.