Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Inappropriate implementation in Workers in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Same Origin Policy bypass in Google Chrome's Workers implementation (versions prior to 149.0.7827.53) allows an unauthenticated remote attacker to violate cross-origin integrity boundaries by luring a victim to a crafted HTML page. The CVSS vector confirms no privileges are required but user interaction is necessary, yielding a High integrity impact with no confidentiality or availability consequence. No public exploit has been identified and EPSS stands at 0.02% (4th percentile), indicating no confirmed active exploitation at time of analysis.
Technical ContextAI
The Web Workers API enables browsers to run JavaScript in background threads, separate from the main UI thread, to avoid blocking. Google Chrome's implementation of this API prior to version 149.0.7827.53 contained an 'inappropriate implementation' - a catch-all category indicating a logic or design flaw rather than a classic memory-safety bug. The root cause is an enforcement gap in the Same Origin Policy (SOP) within the Workers subsystem, meaning a Worker spawned by a crafted page could interact with or influence resources from a different origin in ways the SOP is meant to prevent. The affected product is identified via CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* across all platforms. No CWE has been assigned by NVD, so the precise root cause class (e.g., CWE-346 Origin Validation Error or CWE-284 Improper Access Control) cannot be confirmed from the available data.
RemediationAI
Vendor-released patch: Chrome 149.0.7827.53. Update Google Chrome to version 149.0.7827.53 or later via the browser's built-in update mechanism (Settings > Help > About Google Chrome) or via enterprise deployment tools; the official stable channel release announcement is at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Because the attack requires user interaction (visiting a crafted page), organizations that cannot immediately patch can reduce exposure by enforcing web content filtering to block access to untrusted or newly-registered domains, and by enabling enhanced Safe Browsing in Chrome enterprise policy. Note that content filtering alone does not eliminate risk - it only raises the barrier for delivery. There are no known workarounds that directly mitigate the Workers SOP bypass without patching.
Same weakness CWE-346 – Origin Validation Error
View allSame technique Authentication Bypass
View allVendor StatusVendor
SUSE
| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34445
GHSA-w6p7-cc7p-w2qr