PatchSiren cyber security CVE debrief
CVE-2026-8545 Google CVE debrief
This CVE addresses an object corruption vulnerability in the Compositing component of Google Chrome. The flaw, present in versions prior to 148.0.7778.168, could allow a remote attacker who has already compromised the renderer process to leak cross-origin data through a crafted HTML page. The vulnerability was assigned a High severity rating by Chromium security but received a CVSS 3.1 score of 3.1 (Low) from NVD, reflecting the prerequisite condition of renderer process compromise. The CVE was published on May 14, 2026, and last modified on May 19, 2026. No known exploitation in the wild has been reported, and the vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalog.
- Vendor
- Product
- Chrome
- CVSS
- LOW 3.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-05-14
- Original CVE updated
- 2026-05-19
- Advisory published
- 2026-05-14
- Advisory updated
- 2026-05-19
Who should care
Organizations with managed Chrome deployments, security teams monitoring browser-based attack chains, and developers building security-sensitive web applications should prioritize this patch. The vulnerability is particularly relevant for environments where renderer process compromise is a concern, such as those with users visiting untrusted web content or organizations targeted by sophisticated threat actors employing multi-stage browser exploits.
Technical summary
The vulnerability stems from object corruption within Chrome's Compositing engine, a critical component responsible for layer management and rendering. When exploited, this corruption can be leveraged to leak cross-origin data, violating the same-origin policy that underpins web security. The attack requires prior compromise of the renderer process, meaning this vulnerability serves as an escalation or persistence mechanism rather than an initial entry point. The compositor's role in handling GPU-accelerated rendering and layer compositing makes it a sensitive attack surface, as corruption here can bypass normal isolation boundaries between origins. The fix in version 148.0.7778.168 addresses the underlying object lifecycle or memory management issue in the compositing code path.
Defensive priority
medium
Recommended defensive actions
- Update Google Chrome to version 148.0.7778.168 or later to remediate this vulnerability
- Verify Chrome auto-update is enabled to ensure timely application of security patches
- Review browser security settings and consider site isolation policies as defense-in-depth
- Monitor for unusual renderer process behavior or unexpected cross-origin data access attempts
- Apply principle of least privilege for browser processes where technically feasible
Evidence notes
The CVE description and CPE data confirm this affects Google Chrome versions prior to 148.0.7778.168. The CVSS vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N) indicates network attack vector with high attack complexity, requiring no privileges but user interaction, with low confidentiality impact. The vendor field shows 'Apple' with medium confidence from NVD CPE data, though this appears to be a platform association rather than the affected product vendor.
Official resources
-
CVE-2026-8545 CVE record
CVE.org
-
CVE-2026-8545 NVD detail
NVD
-
Source item URL
nvd_modified
-
Mitigation or vendor reference
[email protected] - Product, Vendor Advisory
-
Source reference
[email protected] - Permissions Required
The vulnerability was disclosed through official Chromium and NVD channels on May 14, 2026, with a stable channel update released to address the issue.