Chrome EUVD-2026-13455

The victim must open a crafted HTML page in Google Chrome versions prior to 146.0.7680.153. WebRTC must be enabled (default). Remote attacker requires no authentication or special privileges.

While CVSS and EPSS scores are not provided in this dataset, the vulnerability exhibits high real-world risk due to multiple factors: (1) the attack vector is NETWORK-based (remote exploitation via crafted HTML), requiring only user interaction to visit a webpage; (2) the Chromium security team classified it as High severity, indicating potential code execution or significant memory safety impact; (3) the vulnerability affects a widely-deployed browser component (WebRTC) used in millions of enterprise and consumer deployments; (4) no exploit complexity is indicated, suggesting straightforward exploitation; (5) a patch exists from the vendor, indicating confirmed reproducibility. The presence of multiple intelligence sources (ENISA EUVD, Chromium issue tracking, Debian tracking) demonstrates this is a tracked, serious vulnerability. This should be treated as a moderate-to-high priority for browser-using organizations, particularly those with users accessing untrusted web content. The availability of a vendor patch reduces urgency but increases expectation for rapid deployment.

An attacker crafts a malicious HTML page containing specially formatted WebRTC data structures or payloads that trigger improper bounds checking in Chrome's WebRTC stack buffer handling. When a user visits this webpage in a vulnerable Chrome browser, the malformed input causes a stack buffer overflow, corrupting adjacent stack memory. This could lead to arbitrary code execution in the context of the browser process, potentially allowing the attacker to steal credentials, capture webcam/microphone input, or compromise the user's system. No public proof-of-concept is indicated in the available sources, but the High severity rating and network-based attack vector suggest the exploitation path is straightforward once the specific buffer overflow offset is identified.