CVE-2026-113032 Google CVE debrief

Who should care

Defenders responsible for managing Google Chrome deployments on Android devices should assess exposure and prioritize updates to prevent potential code execution attacks. This is particularly important for organizations using Chrome on Android devices, as an attacker could exploit this vulnerability via a crafted HTML page. Defenders should review and monitor Chrome usage on Android devices, implement sandboxing and isolation measures for Chrome, and track

Why it matters

CVE-2026-113032 is a memory corruption vulnerability in Google Chrome's Omnibox on Android that could allow remote code execution inside the sandbox. Defenders should prioritize updating Chrome to version 156.0.8078.47 or later to prevent potential attacks. This is particularly important for organizations using Chrome on Android devices, as an attacker could exploit this vulnerability via a crafted HTML page.

• Remote code execution inside the sandbox
• Potential for attacker exploitation
• Need for urgent patching and verification

Technical summary

The memory corruption vulnerability in Google Chrome's Omnibox on Android prior to version 156.0.8078.47 could allow a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. This issue is tracked as CVE-2026-113032 and has a Chromium security severity rating of Medium. The vulnerability affects Google Chrome on Android devices, and defenders should prioritize updating Chrome to version 156.0.8078.47 or later to prevent potential code execution attacks. The CVE record and source item provide details about the memory corruption vulnerability in Google Chrome's Omnibox on Android.

Defensive priority

Defenders should prioritize updating Google Chrome to version 156.0.8078.47 or later to prevent potential code execution attacks. This is particularly important for organizations that use Chrome on Android devices.

Recommended defensive actions

• Update Google Chrome to version 156.0.8078.47 or later
• Review and monitor Chrome usage on Android devices
• Implement sandboxing and isolation measures for Chrome
• 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 about the memory corruption vulnerability in Google Chrome's Omnibox on Android. The issue was publicly disclosed on October 20, 2026, and the CVE record was last modified on October 21, 2026. The Chromium security severity is rated 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.