EUVD-2026-34666
GHSA-w78w-pw3g-jj3f
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
4DescriptionCVE.org
Insufficient validation of untrusted input in Chrome for iOS in Google Chrome on iOS prior to 149.0.7827.53 allowed a remote attacker who convinced a user to engage in specific UI gestures to inject arbitrary scripts or HTML (UXSS) via a crafted QR code. (Chromium security severity: Medium)
AnalysisAI
Universal Cross-Site Scripting (UXSS) in Google Chrome for iOS prior to 149.0.7827.53 allows a remote, unauthenticated attacker to inject arbitrary scripts or HTML across origin boundaries by delivering a crafted QR code and convincing the target to perform specific UI gestures within the browser. The CVSS Scope:Changed rating confirms this bypasses the same-origin policy, meaning injected scripts can access sessions and data from other open origins. No public exploit code has been identified at time of analysis, and the EPSS score of 0.07% (22nd percentile) indicates low observed exploitation probability, though the attack is fully network-accessible once social engineering is achieved. Note: the 'RCE' tag attached to this CVE is inconsistent with the description, which describes UXSS - not OS-level code execution - and should be treated as a tagging error.
Technical ContextAI
The root cause is CWE-20 (Improper Input Validation): Chrome for iOS fails to adequately sanitize input derived from QR code content before processing it in a browser context. QR codes can encode arbitrary URLs or data that Chrome's iOS-specific QR scanning integration may parse and act upon; when user UI gestures trigger navigation or rendering of this content, the insufficient validation allows attacker-supplied scripts or HTML to execute within the browser's privileged context. The CVSS vector's S:C (Scope Changed) component is the critical indicator here - it confirms the injected script executes in a security context different from the originating resource, effectively breaking the same-origin policy and classifying this as UXSS. The CWE-20 classification places the root cause at the input-handling layer rather than a memory safety issue, making this a logic or sanitization flaw in the iOS-specific QR feature. Affected product per EUVD is Chrome on iOS versions below 149.0.7827.53.
RemediationAI
The primary fix is to update Google Chrome on iOS to version 149.0.7827.53 or later, which is confirmed available per the vendor advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Users should update via the Apple App Store. If immediate update is not possible, a practical compensating control is to disable or avoid using Chrome's built-in QR code scanner feature on iOS, instead relying on the native iOS camera app for QR scanning - this removes the vulnerable input-handling path entirely, though it reduces convenience. Organizations managing iOS devices via MDM can enforce Chrome version floors to ensure compliant versions are deployed. Given that exploitation requires active user participation in specific UI gestures, user awareness training about scanning QR codes from untrusted physical or digital sources also serves as a meaningful risk reduction measure. No significant functional side effects are expected from the patch itself.
Same weakness CWE-20 – Improper Input Validation
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today