CVE-2026-113125 Google CVE debrief

Who should care

Defenders responsible for managing Google Chrome deployments, particularly in environments where users access the internet or open untrusted HTML pages, should assess exposure and apply patches.

Why it matters

This vulnerability allows remote attackers to execute arbitrary code within the Chrome sandbox via a crafted HTML page. Defenders should verify exposure, apply patches, and monitor for suspicious activity.

• Potential code execution within the Chrome sandbox
• Requires verification of Chrome version and exposure
• Patching and updating Chrome to version 156.0.8078.47 or later

Technical summary

The vulnerability is caused by a memory corruption issue in Google Chrome's DevTools. This could allow a remote attacker to execute arbitrary code within the sandbox via a crafted HTML page. The issue was addressed in Chrome version 156.0.8078.47. The Chromium security team has assessed this vulnerability as having a Low severity. Defenders should prioritize verifying exposure and applying patches, as this vulnerability could allow code execution within the Chrome sandbox. Additionally, defenders should review compensating controls for exposed systems and monitor for suspicious activity.

Defensive priority

Defenders should prioritize verifying exposure and applying patches, as this vulnerability could allow code execution within the Chrome sandbox.

Recommended defensive actions

• Verify Chrome version and apply patch if necessary
• Monitor for suspicious HTML pages
• Implement sandboxing and isolation measures
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to vendor advisories. The vulnerability was addressed in Chrome version 156.0.8078.47. There are no known instances of this vulnerability being exploited in the wild. However, defenders should still verify exposure and apply patches as a precautionary measure.

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.