CVE-2026-113091 Google CVE debrief

Who should care

Defenders responsible for managing and securing Google Chrome installations on Android devices should assess exposure and apply patches as needed. This includes reviewing and updating inventory of Chrome installations on Android devices, monitoring for suspicious activity related to this vulnerability, and verifying exposure. Security teams and vulnerability management teams should prioritize patching and verifying exposure to prevent exploitation.

Why it matters

CVE-2026-113091 is a use-after-free vulnerability in Google Chrome's PerformanceAPIs on Android, allowing remote code execution inside the sandbox. Defenders should prioritize patching and verifying exposure to prevent exploitation.

• Remote attackers could execute arbitrary code inside the sandbox, potentially leading to unauthorized actions
• Defenders need to verify exposure and apply patches to prevent exploitation
• Successful exploitation requires user interaction via a crafted HTML page

Technical summary

A use-after-free vulnerability exists in the PerformanceAPIs of Google Chrome on Android prior to version 156.0.8078.47. This vulnerability allows a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. The vulnerability has a low severity rating according to Chromium security severity standards. Defenders should prioritize verifying exposure and applying patches to prevent exploitation. The affected product context is Google Chrome on Android, and the defensive impact is the potential for remote code execution inside the sandbox.

Defensive priority

Defenders should prioritize verifying exposure and applying patches for Google Chrome on Android, as a remote attacker could exploit this vulnerability to execute arbitrary code inside the sandbox.

Recommended defensive actions

• Verify and apply the patch for Google Chrome on Android (version 156.0.8078.47 or later)
• Review and update inventory of Chrome installations on Android devices
• Monitor for suspicious activity related to this vulnerability
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• 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

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to additional information. The vulnerability exists in Google Chrome on Android prior to version 156.0.8078.47. Defenders should verify exposure and apply patches as needed. The source item and CVE record provide supplemental details, but evidence limits and unknown affected scope should be considered. Official sources such as CVE Program and NIST NVD provide additional context.

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.