CVE-2026-11217
Analyzed Analyzed - Analysis Complete
Inappropriate Implementation in Fenced Frames in Google Chrome

Publication date: 2026-06-04

Last updated on: 2026-06-05

Assigner: Chrome

Description
Inappropriate implementation in Fenced Frames in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Low)
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-04
Last Modified
2026-06-05
Generated
2026-06-25
AI Q&A
2026-06-05
EPSS Evaluated
2026-06-24
NVD
CVE-2026-11217
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
google chrome to 149.0.7827.53 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-346 The product does not properly verify that the source of data or communication is valid.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is an inappropriate implementation in Fenced Frames in Google Chrome versions prior to 149.0.7827.53. It allows a remote attacker who has already compromised the renderer process to bypass site isolation by using a specially crafted HTML page.

Impact Analysis

If exploited, this vulnerability could allow an attacker to bypass site isolation protections in Google Chrome, potentially enabling them to access or manipulate data from other sites or browser contexts that should be isolated. This could lead to unauthorized data exposure or other security risks.

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