CVE-2010-0643: Google Chrome before 4.0.249.89 attempts to make direct connections to web sites when all configured proxy...

Security readout for executives and security teams

Older Google Chrome versions could bypass configured proxies if all proxies were unavailable, connecting directly to websites. That could expose a user's real network identity in normal web server logs, especially where the proxy was used for anonymity. This is a privacy and policy-bypass issue, not a disclosed code-execution flaw. Exposure is mainly legacy Chrome installations, especially systems relying on proxies for anonymity, privacy, egress control, or source-address masking. Modern managed browser fleets are unlikely to be affected unless outdated binaries remain in use. Treat this as a legacy privacy exposure. Prioritize remediation where proxy use is tied to anonymity, regulated investigations, or strict egress policy. It is less urgent than remote code execution but still relevant for environments with old browser images. Mitigation focus: Upgrade any legacy Chrome installation to 4.0.249.89 or later.; Check current vendor guidance for any remaining supported remediation details.; Audit managed endpoints for obsolete Chrome binaries..

Prepared

Jun 28, 2026, 09:59 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.