Skip to content
VulniPulse
Sign in
Advisory severityHigh8.7Red Hat Linux

High [CVE-2026-76033] Site isolation bypass due to inappropriate CORS implementation

This high-severity Red Hat Linux advisory covers CVE-2026-76033.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-76033 Source published Source updated

VulniPulse record published Record updated

CVE-2026-76033
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

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) A flaw was found in Google Chrome's handling of Cross-Origin Resource Sharing (CORS).

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. This could lead to unauthorized access to sensitive data from other websites, significantly undermining a core browser security boundary.

Red Hat severity: Important — CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N). Weakness: CWE-653.

Affected versions
  • < 151.0.7922.169

Official advisory · high-confidence parse· fetched 22 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 22 days ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 22 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.