CVE-2026-17767 Google CVE debrief

Who should care

Defenders responsible for Google Chrome on Android devices should assess exposure and prioritize patching to prevent potential cross-origin data leaks. This includes reviewing incident response plans, verifying and applying patches, and monitoring for potential security issues. Additionally, defenders should review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

CVE-2026-17767 is a medium-severity vulnerability in Google Chrome on Android that allows a remote attacker to leak cross-origin data. Defenders should prioritize patching and monitoring to prevent potential security incidents.

• Verify and apply patches to prevent cross-origin data leaks
• Monitor for potential security issues in Google Chrome on Android devices
• Review incident response plans to address potential security incidents

Technical summary

Insufficient validation of untrusted input in WebView in Google Chrome on Android prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. This vulnerability affects Google Chrome on Android devices, specifically those with versions prior to 151.0.7922.72. The vulnerability allows a remote attacker to leak cross-origin data, potentially leading to security incidents. Defenders should prioritize patching and monitoring to prevent potential security incidents.

Defensive priority

Defenders should prioritize verifying and applying the patch to ensure the security of Google Chrome on Android devices.

Recommended defensive actions

• Verify and apply the patch to Google Chrome on Android devices
• Monitor Google Chrome on Android devices for potential security issues
• Review and update incident response plans to address potential cross-origin data leaks
• 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 NVD vulnerability detail page provide information on the vulnerability, including its description, CVSS score, and affected versions. The CVE record was published on 2026-07-30T01:16:39.880Z and has not been modified since then. The vulnerability has a CVSS score of 4.3 and is classified as Medium severity. The affected product is Google Chrome on Android prior to version 151.0.7922.72.

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.