EUVD-2026-34487
GHSA-r63x-j58x-h6jq
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Insufficient policy enforcement in Subresource Integrity in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass content security policy via malicious network traffic. (Chromium security severity: Medium)
AnalysisAI
Subresource Integrity (SRI) policy enforcement failure in Google Chrome prior to 149.0.7827.53 enables remote attackers to bypass Content Security Policy protections via malicious network traffic. Affected users who visit attacker-influenced pages may have tampered scripts or resources loaded without the expected cryptographic hash validation that SRI is designed to enforce, undermining integrity guarantees that web applications depend on as a security boundary. No active exploitation is confirmed (not in CISA KEV), EPSS is very low at 0.02% (6th percentile), and a vendor patch is available at 149.0.7827.53.
Technical ContextAI
Subresource Integrity is a W3C browser security mechanism allowing web pages to specify cryptographic hashes via integrity= attributes on <script> and <link> tags; the browser is expected to block resources whose content does not match the declared hash, particularly when paired with a Content Security Policy. CWE-20 (Improper Input Validation) identifies the root cause as Chrome's SRI enforcement logic failing to properly validate or act on policy constraints under certain network conditions, rather than a memory corruption or logic flaw. The vulnerability resides in Chrome's Blink rendering engine SRI subsystem. Based on ENISA EUVD-2026-34487 and the NVD CPE-implied scope, all desktop Chrome versions prior to 149.0.7827.53 on Windows, macOS, and Linux are affected. No CPE strings were explicitly provided in the input data.
RemediationAI
Update Google Chrome to version 149.0.7827.53 or later immediately, as detailed in the vendor stable channel advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Enterprise environments using Google's managed Chrome update infrastructure (via Google Admin Console or enterprise MSI/PKG deployments) should push this update as a priority patch cycle. The patch is confirmed available per vendor advisory; no independently verified alternative release versions or backports are noted in the available data. As a compensating control prior to patching in high-sensitivity environments, administrators can consider deploying network-layer controls (e.g., DNS filtering or proxy policies) to restrict access to untrusted external origins for internal web applications that depend on SRI for integrity enforcement - note this does not eliminate risk from on-path attackers and will break legitimate third-party resource loading. Disabling JavaScript broadly is not a practical mitigation due to severe application breakage. No significant side effects from applying the vendor patch have been noted.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today