CVE-2026-11037
A memory corruption bug in Google Chrome’s video codec can let a remote attacker escape the browser sandbox by opening a specially crafted video file. The flaw is in versions before 149.0.7827.53 and could allow attackers to run arbitrary code on the victim’s machine. It is considered critical because it can be triggered over the network with no user interaction.
No official fix yet. If none appears within 45 days of first tracking, this entry is removed automatically.
Who is affected
Users of Google Chrome versions earlier than 149.0.7827.53 on any operating system (Windows, macOS, Linux).
Real-world impact
An attacker could gain full control of the victim’s computer by tricking them into opening a malicious video file, potentially stealing data or installing malware.
Why this severity
The CVSS score of 9.6 reflects that the vulnerability can be exploited remotely (AV:N), requires no special privileges (PR:N), needs no user interaction (UI:R), and gives the attacker complete compromise of confidentiality, integrity, and availability (C:H/I:H/A:H).
What to do about it
- ›Check for and install the latest Google Chrome update when it becomes available.
No official fix or mitigation is documented in the sources yet. Monitor the vendor advisory and apply the patch as soon as it is released.
No fix documented in sources
Timeline
- Jun 4, 2026 · Jun 4, 2026PublishedDisclosed and added to the National Vulnerability Database.
- Jul 23, 2026 · 12d agoAdvisory updatedThe NVD record was last revised.
How it’s attacked
References & advisories
- chromereleases.googleblog.com/2026/06/stable-channel-upda…vendor advisory
- issues.chromium.org/issues/497971287permissions required