CVE-2009-2121: Buffer overflow in the browser kernel in Google Chrome before 2.0.172.33 allows remote HTTP servers to caus...

Security readout for executives and security teams

CVE-2009-2121 affects Google Chrome before 2.0.172.33. A malicious or compromised HTTP server could trigger a browser-kernel buffer overflow through a crafted response, causing Chrome to crash or possibly run attacker-controlled code. This mainly matters for legacy systems, kiosks, lab images, or archived virtual machines still using very old Chrome builds. Exposure is likely limited to systems running Google Chrome earlier than 2.0.172.33, especially unmanaged legacy endpoints, test environments, embedded browser deployments, and old VM snapshots. Current Chrome deployments are not indicated as affected by the provided sources. Treat this as high priority only where old Chrome is still present. For normal modern fleets, priority is mainly verification and legacy cleanup. The business risk is browser compromise or service disruption on obsolete systems that may be overlooked by standard patch reporting. Mitigation focus: Upgrade any Chrome installation below 2.0.172.33 to 2.0.172.33 or later.; Remove unsupported legacy Chrome builds from endpoints, kiosks, and golden images.; Check vendor release notes before relying on compensating controls..

Prepared

Jun 28, 2026, 10:45 UTC (UTC+00:00)

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