CVE-2026-4463: Heap buffer overflow in WebRTC
Chromium: CVE-2026-4463 Heap buffer overflow in WebRTC
Other sources
Heap buffer overflow in WebRTC in Google Chrome prior to 146.0.7680.153 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
— NVD
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information.
— Microsoft
Credit
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-4439
- CVE-2026-4440
- CVE-2026-4441
- CVE-2026-4442
- CVE-2026-4443
- CVE-2026-4444
- CVE-2026-4445
- CVE-2026-4446
- CVE-2026-4447
- CVE-2026-4448
- CVE-2026-4449
- CVE-2026-4450
- CVE-2026-4451
- CVE-2026-4452
- CVE-2026-4453
- CVE-2026-4454
- CVE-2026-4455
- CVE-2026-4456
- CVE-2026-4457
- CVE-2026-4458
- CVE-2026-4459
- CVE-2026-4460
- CVE-2026-4461
- CVE-2026-4462
- CVE-2026-4464
Frequently Asked Questions
What is the severity of CVE-2026-4463?
CVE-2026-4463 has a severity rating of High due to its potential for heap corruption exploitation.
How do I fix CVE-2026-4463?
To fix CVE-2026-4463, update your Google Chrome to version 146.0.7680.153 or later.
Which versions of Google Chrome are affected by CVE-2026-4463?
Google Chrome versions prior to 146.0.7680.153 are affected by CVE-2026-4463.
Can CVE-2026-4463 affect other browsers?
CVE-2026-4463 specifically affects Google Chrome and Microsoft Edge (Chromium-based) prior to specified versions.
What type of vulnerability is CVE-2026-4463?
CVE-2026-4463 is classified as a heap buffer overflow vulnerability.