CVE-2026-113292 Google CVE debrief

Who should care

Defenders responsible for managing Google Chrome on Android devices should assess exposure and prioritize updating to version 156.0.8078.47 or later. They should also review and implement additional security measures to prevent sandbox escapes and monitor for potential crafted HTML pages that could exploit this vulnerability. Security teams should verify and update Google Chrome on Android to version 156.0.8078.47 or later and track exceptions, retest rem

Why it matters

CVE-2026-113292 is a Low-severity vulnerability in Google Chrome's Omnibox on Android that could allow remote code execution inside the sandbox. Defenders should prioritize verifying and updating Google Chrome on Android to version 156.0.8078.47 or later, and monitor for potential crafted HTML pages that could exploit this vulnerability.

• Potential execution of arbitrary code inside the sandbox
• Verification of Google Chrome version on Android devices
• Monitoring for crafted HTML pages that could exploit this vulnerability
• Implementation of additional security measures to prevent sandbox escapes

Technical summary

The vulnerability is caused by improper input validation in Google Chrome's Omnibox on Android prior to version 156.0.8078.47. This could potentially allow a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. The Chromium security severity is rated as Low. Defenders should prioritize verifying and updating Google Chrome on Android to version 156.0.8078.47 or later, and monitor for potential crafted HTML pages that could exploit this vulnerability. The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to additional information.

Defensive priority

Defenders should prioritize verifying and updating Google Chrome on Android to version 156.0.8078.47 or later, and monitor for potential crafted HTML pages that could exploit this vulnerability.

Recommended defensive actions

• Verify and update Google Chrome on Android to version 156.0.8078.47 or later
• Monitor for potential crafted HTML pages that could exploit this vulnerability
• Review and implement additional security measures to prevent 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
• 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 description, affected versions, and references to additional information. However, the CVSS score and severity are not provided.

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.