<Vulnerability name="CVE-2026-76033">
    <DocumentDistribution xml:lang="en">Copyright © 2012 Red Hat, Inc. All rights reserved.</DocumentDistribution>
    <ThreatSeverity>Important</ThreatSeverity>
    <PublicDate>2026-08-18T20:31:25</PublicDate>
    <Bugzilla id="2518270" url="https://bugzilla.redhat.com/show_bug.cgi?id=2518270" xml:lang="en:us">
chromium-browser: Google Chrome: Site isolation bypass due to inappropriate CORS implementation
    </Bugzilla>
    <CVSS3 status="draft">
        <CVSS3BaseScore>8.7</CVSS3BaseScore>
        <CVSS3ScoringVector>CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N</CVSS3ScoringVector>
    </CVSS3>
    <CWE>CWE-653</CWE>
    <Details xml:lang="en:us" source="Mitre">
Inappropriate implementation in CORS in Google Chrome prior to 151.0.7922.169 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: High)
    </Details>
    <Details xml:lang="en:us" source="Red Hat">
A flaw was found in Google Chrome's handling of Cross-Origin Resource Sharing (CORS). A remote attacker, who has already compromised the browser's renderer process, could exploit this vulnerability by using a specially crafted HTML page. This could allow the attacker to bypass site isolation, a security feature designed to prevent malicious websites from accessing data from other websites, potentially leading to unauthorized data access.
    </Details>
    <Statement xml:lang="en:us">
This Important flaw in chromium-browser allows a remote attacker to bypass site isolation after an initial compromise of the browser's renderer process. This could lead to unauthorized access to sensitive data from other websites, significantly undermining a core browser security boundary.
    </Statement>
    <References xml:lang="en:us">
https://www.cve.org/CVERecord?id=CVE-2026-76033
https://nvd.nist.gov/vuln/detail/CVE-2026-76033
https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0826575033.html
https://issues.chromium.org/issues/516715010
    </References>
</Vulnerability>