CVE-2026-4463
Received Received - Intake

Heap Buffer Overflow in Chrome WebRTC Enables Remote Exploit

Publication date: 2026-03-20

Last updated on: 2026-03-20

Assigner: Chrome

Description
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)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-03-20
Last Modified
2026-03-20
Generated
2026-07-06
AI Q&A
2026-03-20
EPSS Evaluated
2026-07-05
NVD
CVE-2026-4463
EUVD
EUVD-2026-13480

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 146.0.7680.153 (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 146.0.7680.153. It allows a remote attacker to potentially cause heap corruption by using a specially crafted HTML page.

Impact Analysis

The vulnerability can lead to heap corruption, which may allow a remote attacker to execute arbitrary code or cause a denial of service in the affected version of Google Chrome.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant

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

EPSS Chart