CVE-2026-17799 Google CVE debrief

Who should care

Organizations and individuals using Google Chrome versions prior to 151.0.7922.72 should apply patches or updates to address this vulnerability. This includes administrators responsible for Chrome deployments in enterprise environments, IT teams managing browser updates, and individual users who rely on Chrome for their daily browsing activities. Additionally, security teams should review and verify the affected scope within their organizations and prioritize patching to prevent potential bypass of discretionary access control.

Technical summary

Insufficient validation of untrusted input in Safe Browsing in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to bypass discretionary access control via a malicious file. This vulnerability affects Google Chrome's Safe Browsing feature, which is designed to protect users from malicious content. The insufficient validation could enable attackers to craft malicious files that might bypass access controls, potentially leading to unauthorized actions.

Defensive priority

Medium severity vulnerability in Google Chrome, requiring immediate attention to prevent potential bypass of discretionary access control.

Recommended defensive actions

• Inventory and verify Google Chrome versions prior to 151.0.7922.72
• Apply patches or updates to Google Chrome to address insufficient validation vulnerability
• Monitor for potential malicious files attempting to bypass discretionary access control
• 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

Evidence from official sources indicates insufficient validation of untrusted input in Safe Browsing in Google Chrome prior to 151.0.7922.72. However, details on affected scope and potential impact are limited. Defenders should verify Chrome versions, review official advisories, and monitor for potential malicious files attempting to bypass discretionary access control. Additional evidence from Chromium issue tracker and Chrome release blog posts may provide further context.

Official resources