CVE-2026-5919
Received Received - Intake
WebSocket Input Validation Bypass in Chrome Renderer Process

Publication date: 2026-04-08

Last updated on: 2026-04-29

Assigner: Chrome

Description
Insufficient validation of untrusted input in WebSockets in Google Chrome prior to 147.0.7727.55 allowed a remote attacker who had compromised the renderer process to bypass same origin policy via a crafted HTML page. (Chromium security severity: Low)
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-08
Last Modified
2026-04-29
Generated
2026-06-16
AI Q&A
2026-04-09
EPSS Evaluated
2026-06-15
NVD
CVE-2026-5919
EUVD
EUVD-2026-20754
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 147.0.7727.55 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability involves insufficient validation of untrusted input in the WebSockets implementation of Google Chrome versions prior to 147.0.7727.55. It allows a remote attacker, who has already compromised the renderer process, to bypass the same origin policy by using a specially crafted HTML page.

Impact Analysis

If exploited, this vulnerability could allow an attacker to bypass the same origin policy, potentially enabling them to access or manipulate data from other origins within the browser. This could lead to unauthorized data access or actions within the context of the compromised renderer process.

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