CVE-2026-113204 Google CVE debrief

Who should care

Defenders responsible for managing and securing Google Chrome installations on Android devices should assess exposure and prioritize patching. This includes IT teams, security teams, and administrators responsible for maintaining Chrome deployments on Android devices. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and plan vendor-supported updates or mitigations through normal and

Why it matters

CVE-2026-113204 is a medium-severity use-after-free vulnerability in Google Chrome's TrustedWebActivities on Android. Defenders should prioritize patching to version 156.0.8078.47 or later, monitor for exploitation attempts, and verify Chrome updates. Evidence from official sources supports the vulnerability's existence and potential impact.

• Potential for remote code execution inside the sandbox requires immediate patching and monitoring.
• Exposure of Chrome on Android devices to crafted HTML pages could lead to exploitation attempts.
• Verification of Chrome version and update processes is necessary to ensure mitigation.
• Restricting exploitation attempts and monitoring for suspicious activity is advised.

Technical summary

The CVE record describes a use-after-free vulnerability in TrustedWebActivities in Google Chrome on Android prior to 156.0.8078.47. This vulnerability could allow a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. The vulnerability affects Google Chrome installations on Android devices and is classified as medium-severity. Defenders should prioritize patching to version 156.0.8078.47 or later and monitor for exploitation attempts. The vulnerability's existence and potential impact are supported by evidence from official sources.

Defensive priority

Medium

Recommended defensive actions

• Review and apply the available patch for Google Chrome on Android to version 156.0.8078.47 or later.
• Monitor for and restrict exploitation attempts targeting this vulnerability.
• Verify that Chrome is up-to-date on all Android devices.
• Consider implementing sandboxing and isolation measures for high-risk applications like 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.

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to additional information. Official sources, including the CVE Program and NIST NVD, confirm the vulnerability's existence and provide guidance on affected versions and mitigation strategies. The evidence suggests that defenders should verify Chrome updates, monitor for exploitation attempts, and restrict exposure to crafted HTML pages.

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.