CVE-2026-12447
Awaiting Analysis Awaiting Analysis - Queue
Heap Buffer Overflow in Google Chrome WebRTC

Publication date: 2026-06-17

Last updated on: 2026-06-17

Assigner: Chrome

Description
Heap buffer overflow in WebRTC in Google Chrome prior to 149.0.7827.155 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-17
Last Modified
2026-06-17
Generated
2026-06-17
AI Q&A
2026-06-17
EPSS Evaluated
N/A
NVD
CVE-2026-12447
EUVD
EUVD-2026-37532
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 149.0.7827.155 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-122 A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a heap buffer overflow in the WebRTC component of Google Chrome versions prior to 149.0.7827.155. It allows a remote attacker to execute arbitrary code inside a sandbox by tricking a user into visiting a specially crafted HTML page.

Impact Analysis

An attacker exploiting this vulnerability could run arbitrary code on your device within the sandbox environment. This could lead to unauthorized actions such as data theft, system compromise, or further attacks, potentially affecting the confidentiality, integrity, and availability of your system.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-12447. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart