Google Chrome tests real-time Safe Browsing checks for Incognito and Guest modes
Google is developing an experimental change that would extend Chrome's real-time Safe Browsing checks to Incognito and Guest windows, which can currently fall back to a locally stored list of unsafe sites (dataconomy.com). The change was spotted in Chromium development records and reported by Windows Report (windowsreport.com). According to Dataconomy, the feature is disabled by default behind an experimental Chrome flag, and Google has not announced a public release date or confirmed when it will reach stable builds (dataconomy.com). The article states that the patch is already merged into the main branch and will reach all desktop and mobile installations; I could not verify that claim, and the Chromium code review it cites was not among the pages opened. The risk to defenders is limited: this is a privacy-preserving protection enhancement, not a vulnerability, and no exploitation or threat actor is involved.
Detalhes técnicos
The proposed design covers both Standard and Enhanced Safe Browsing protection (windowsreport.com). Under Standard Protection, Chrome normally checks a local list of known-safe sites before an online lookup through a privacy server, and that server obscures the user's IP address during routine checks (dataconomy.com). Chromium records indicate that the temporary security-key updates generated during Incognito sessions would stay in memory and would not be written to device storage (dataconomy.com). The article also describes truncated hashed lookups, a multi-hop privacy proxy relay and an operating system purge of RAM at session end. None of these details appear in the pages I opened, so they are article-only claims.
Remediação
No patch or user action is required for a vulnerability, because none is described. Defenders should keep Chrome on the current stable release and confirm which Safe Browsing level is configured on managed endpoints. Enterprises should watch for the feature when it reaches stable builds, since it is off by default and no release date has been set (dataconomy.com).
Relatos divergentes
The article says the patch is merged into the main branch and that public releases will deliver the capability to all desktop and mobile installations. Dataconomy, citing Chromium development records, reports that the feature remains disabled by default behind an experimental flag with no announced public release date (dataconomy.com). The more recent and specific source on availability is Dataconomy, and no Google statement was found to settle the question.
Linha do tempo
-
Google Chrome tests real-time Safe Browsing checks for Incognito and Guest modes
ler a análise desta fonte ocultar
Google is developing an experimental change that would extend Chrome's real-time Safe Browsing checks to Incognito and Guest windows, which can currently fall back to a locally stored list of unsafe sites (dataconomy.com). The change was spotted in Chromium development records and reported by Windows Report (windowsreport.com). According to Dataconomy, the feature is disabled by default behind an experimental Chrome flag, and Google has not announced a public release date or confirmed when it will reach stable builds (dataconomy.com). The article states that the patch is already merged into the main branch and will reach all desktop and mobile installations; I could not verify that claim, and the Chromium code review it cites was not among the pages opened. The risk to defenders is limited: this is a privacy-preserving protection enhancement, not a vulnerability, and no exploitation or threat actor is involved.
Technical Details
The proposed design covers both Standard and Enhanced Safe Browsing protection (windowsreport.com). Under Standard Protection, Chrome normally checks a local list of known-safe sites before an online lookup through a privacy server, and that server obscures the user's IP address during routine checks (dataconomy.com). Chromium records indicate that the temporary security-key updates generated during Incognito sessions would stay in memory and would not be written to device storage (dataconomy.com). The article also describes truncated hashed lookups, a multi-hop privacy proxy relay and an operating system purge of RAM at session end. None of these details appear in the pages I opened, so they are article-only claims.
Remediation
No patch or user action is required for a vulnerability, because none is described. Defenders should keep Chrome on the current stable release and confirm which Safe Browsing level is configured on managed endpoints. Enterprises should watch for the feature when it reaches stable builds, since it is off by default and no release date has been set (dataconomy.com).
Conflicting Reports
The article says the patch is merged into the main branch and that public releases will deliver the capability to all desktop and mobile installations. Dataconomy, citing Chromium development records, reports that the feature remains disabled by default behind an experimental flag with no announced public release date (dataconomy.com). The more recent and specific source on availability is Dataconomy, and no Google statement was found to settle the question.