CVE-2026-113195 Google CVE debrief

Who should care

Defenders responsible for managing Google Chrome deployments should assess exposure and prioritize updating to the fixed version. This includes IT teams managing Chrome installations, security teams monitoring for potential sandbox escapes, and operators responsible for reviewing and implementing compensating controls for sandboxing. Defenders should also review the supplied official advisory or CVE record to validate affected scope, severity, and vendor

Why it matters

CVE-2026-113195 is a Medium-severity vulnerability in Google Chrome that could allow potential arbitrary code execution inside the sandbox. Defenders should prioritize verifying Chrome versions, updating to the fixed version, and monitoring for potential sandbox escapes.

• Potential arbitrary code execution inside the sandbox requires verification of Chrome versions and updating to the fixed version.
• Monitoring for potential sandbox escapes is necessary to prevent further exploitation.
• Defenders should review and implement compensating controls for sandboxing to limit the attack surface.

Technical summary

The vulnerability is caused by improper input validation in the Downloads feature of Google Chrome prior to version 156.0.8078.47. A remote attacker could potentially execute arbitrary code inside the sandbox via a crafted HTML page. The vulnerability has a Medium severity and defenders should prioritize verifying Chrome versions and updating to the fixed version. Monitoring for potential sandbox escapes is necessary to prevent further exploitation. Defenders should review and implement compensating controls for sandboxing to limit the attack surface.

Defensive priority

Defenders should prioritize verifying Chrome versions and updating to 156.0.8078.47 or later, as well as monitoring for potential sandbox escapes.

Recommended defensive actions

• Verify Chrome version and update to 156.0.8078.47 or later
• Monitor for potential sandbox escapes
• Review and implement compensating controls for sandboxing
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• 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
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and references to vendor advisories. The vulnerability has a Medium severity and is caused by improper input validation in the Downloads feature of Google Chrome. The CVE record was published on 2026-10-20T21:02:18.253Z and has not been modified since then. The NVD entry is currently unclassified. Defenders should verify Chrome versions and update to the fixed version.

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.