CVE-2026-6313
Received Received - Intake
CORS Policy Bypass in Google Chrome Renderer Causes Data Leak

Publication date: 2026-04-15

Last updated on: 2026-04-17

Assigner: Chrome

Description
Insufficient policy enforcement in CORS in Google Chrome prior to 147.0.7727.101 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-15
Last Modified
2026-04-17
Generated
2026-06-16
AI Q&A
2026-04-15
EPSS Evaluated
2026-06-14
NVD
CVE-2026-6313
EUVD
EUVD-2026-23068
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 147.0.7727.101 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is an insufficient policy enforcement issue in the Cross-Origin Resource Sharing (CORS) mechanism in Google Chrome versions prior to 147.0.7727.101. It allows a remote attacker who has compromised the renderer process to leak data from other origins by using a specially crafted HTML page.

Impact Analysis

The vulnerability can lead to unauthorized leakage of cross-origin data, meaning sensitive information from other websites or origins could be exposed to an attacker. This could compromise user privacy and security by allowing attackers to access data they should not have permission to view.

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