# CVE-2026-12466: Google Chrome heap buffer overflow in WebRTC

Source: https://junglewise.ai/threats/cve-2026-12466-google-chrome-heap-buffer-overflow-in-webrtc  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-17. Updated: 2026-06-17  
License: CC BY 4.0 with a link back

CVE-2026-12466 · Severity: high · CVSS 8.8 · Published 2026-06-17

Google Chrome is a widely used web browser. A vulnerability in its WebRTC component, which handles real-time communication like video and audio calls, could allow an attacker to take control of a user's computer. This occurs if a user visits a specially crafted, malicious website, potentially leading to unauthorized data access or system compromise.

Technologies: [Google Chrome](https://junglewise.ai/threats/technologies/chrome). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## Quick answers

**Is CVE-2026-12466 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-12466 being exploited in the wild.

**How severe is CVE-2026-12466?** High severity, with a CVSS score of 8.8, published 17 June 2026.

**Which products and versions are affected?** Google Chrome prior to 149.0.7827.155.

**Is there a fix for CVE-2026-12466?** A patch was published on 2026-06-16: Stable channel update released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-12466 attacked?** It is attacked over the network, in a network appliance.

**Am I affected by CVE-2026-12466?** Check whether you run Google Chrome 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

A heap-based buffer overflow (CWE-122) exists in the WebRTC component of Google Chrome for Windows. The vulnerability is triggered when the browser processes a specially crafted HTML page, allowing a remote attacker to achieve arbitrary code execution within the context of the browser process. The attack vector is network-based and requires minimal user interaction (visiting a malicious site). This issue was addressed in Chrome version 149.0.7827.155.

## Affected products

- Google Chrome prior to 149.0.7827.155

## Timeline

- 2026-06-05: other: Reported to Google
- 2026-06-16: patched: Stable channel update released
- 2026-06-17: disclosed: CVE published

## References

- [https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01750511403.html](https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01750511403.html)
- [https://issues.chromium.org/issues/520199394](https://issues.chromium.org/issues/520199394)

## Related threats

- [Google Chrome out of bounds read in Skia](https://junglewise.ai/threats/cve-2026-126922-out-of-bounds-read-in-skia-in-google-chrome-prior-to-157-0-8103)
- [Google Chrome use after free in Accessibility](https://junglewise.ai/threats/cve-2026-126921-use-after-free-in-accessibility-in-google-chrome-prior-to-157-0)
- [Google Chrome information leak in Skia](https://junglewise.ai/threats/cve-2026-126920-information-leak-in-skia-in-google-chrome-prior-to-157-0-8103-78)
- [Google Chrome use-after-free in BrowserTag](https://junglewise.ai/threats/cve-2026-126919-use-after-free-in-browsertag-in-google-chrome-prior-to-157-0)
- [Google Chrome use-after-free in Layout](https://junglewise.ai/threats/cve-2026-126918-use-after-free-in-layout-in-google-chrome-prior-to-157-0-8103-78)