EUVD-2026-34365
GHSA-8c9m-grgp-37c3
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
5DescriptionCVE.org
Insufficient validation of untrusted input in DevTools in Google Chrome prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to inject arbitrary scripts or HTML (UXSS) via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Universal Cross-Site Scripting (UXSS) in Google Chrome's DevTools component allows an attacker who has already compromised the renderer process to inject arbitrary scripts or HTML across security origins via a crafted HTML page, bypassing the same-origin policy. Affected versions are all Chrome releases prior to 149.0.7827.53. No public exploit code exists and no active exploitation has been observed; this vulnerability functions as a second-stage capability within a broader attack chain requiring prior renderer compromise.
Technical ContextAI
The vulnerability resides in the DevTools component of Google Chrome (Chromium engine), which provides browser-integrated developer tooling such as DOM inspection, JavaScript console, and network monitoring. CWE-20 (Improper Input Validation) indicates that DevTools fails to adequately sanitize or validate untrusted input - in this case, data originating from a renderer process that an attacker controls. UXSS (Universal Cross-Site Scripting) is a class of attack that exploits flaws in the browser itself rather than in web application code, allowing injected scripts to run with the full privileges of any origin, effectively bypassing the Same-Origin Policy. The Chromium renderer process handles web content and is intentionally sandboxed; however, once the renderer is compromised (e.g., via a separate renderer exploit), an adversary can interact with DevTools in ways the browser's validation logic does not anticipate, escalating the compromise to cross-origin script injection. The CVSS scope value of 'Changed' (S:C) reflects this cross-origin impact boundary crossing.
RemediationAI
Update Google Chrome to version 149.0.7827.53 or later, which resolves this vulnerability per the vendor's stable channel update advisory at chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Users and administrators should verify that Chrome's auto-update mechanism has applied this release; on managed enterprise deployments, push the update via Google Admin Console or applicable MDM policy. Because exploitation requires a prior renderer compromise, organizations should also prioritize patching any co-occurring Chrome renderer vulnerabilities as a defense-in-depth measure to eliminate the prerequisite stage of an attack chain. Disabling or restricting access to Chrome DevTools via enterprise policy (e.g., DeveloperToolsAvailability=2 to block access for unmanaged users) is a compensating control that reduces the attack surface but may impact developer workflows and does not constitute a full fix. There are no known workarounds that fully mitigate this vulnerability without patching.
Same weakness CWE-20 – Improper Input Validation
View allSame technique Code Injection
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today