Quick answers
- Is CVE-2026-11668 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-11668 being exploited in the wild.
- How severe is CVE-2026-11668?
- Informational severity, published 9 June 2026.
- Which products and versions are affected?
- Google Chrome prior to 149.0.7827.103; Google ChromeOS prior to 149.0.7827.103.
- Is there a fix for CVE-2026-11668?
- A patch was published on 2026-06-08: Stable channel update released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-11668 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-11668?
- Check whether you run Google Chrome or Google ChromeOS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An uninitialized use vulnerability (CWE-457) exists in the Codecs component of Google Chrome and ChromeOS. The flaw is triggered when the browser processes a specially crafted video file. A remote attacker can exploit this to leak cross-origin data, potentially bypassing Same-Origin Policy (SOP) protections. The vulnerability was reported by Google internal researchers and is addressed in Chrome version 149.0.7827.102 for Linux and 149.0.7827.103 for ChromeOS. Attackers require no special privileges, but must entice a user to visit a malicious site or load a malicious video asset.
Affected products
- Google ChromeOS prior to 149.0.7827.103
- Google Chrome prior to 149.0.7827.102 (Linux)
Timeline
- 2026-05-21: disclosed: Reported by Google researchers
- 2026-06-08: patched: Stable channel update released
- 2026-06-09: advisory: NVD publication date