Severity by source
AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Integer overflow in Chromoting in Google Chrome on Windows prior to 149.0.7827.53 allowed a local attacker to obtain potentially sensitive information from process memory via a crafted ETW event. (Chromium security severity: Low)
AnalysisAI
Integer overflow in Chrome's Chromoting (Remote Desktop) component on Windows exposes process memory contents to local authenticated attackers via crafted ETW (Event Tracing for Windows) events. Affected versions are all Chrome releases on Windows prior to 149.0.7827.53. With CVSS confidentiality impact rated High and no public exploit identified at time of analysis, the practical risk is constrained by the local access and user interaction requirements, though sensitive data such as credentials or session tokens resident in process memory could be disclosed. EPSS score of 0.01% (1st percentile) confirms low observed exploitation probability.
Technical ContextAI
Chromoting is the underlying protocol and component powering Google's Chrome Remote Desktop service, bundled with the Chrome browser on Windows. The vulnerability is an integer overflow (described as such in the CVE, though the assigned CWE-472 - 'External Control of Assumed-Immutable Web Parameter' - appears mismatched and likely reflects a data-quality issue in the CWE assignment; CWE-190 would be the canonical class for integer overflows). ETW (Event Tracing for Windows) is a high-performance kernel-level tracing subsystem; Chromoting consumes ETW events for logging or telemetry purposes on Windows. When processing a specially crafted ETW event, an integer overflow in the length or offset calculation allows the component to read beyond intended memory boundaries, surfacing contents of the process's address space to the attacker. The vulnerability is Windows-platform-specific and does not affect Chrome on Linux, macOS, Android, or ChromeOS. Affected CPE inferred from EUVD data: all Google Chrome releases on Windows prior to version 149.0.7827.53.
RemediationAI
Update Google Chrome on Windows to version 149.0.7827.53 or later, which contains the vendor-released fix. The advisory is available at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome's auto-update mechanism will deploy this for most users; administrators managing enterprise fleets should verify deployment via Chrome Browser Cloud Management or Group Policy. As a compensating control where immediate patching is not possible, organizations can disable or uninstall the Chrome Remote Desktop (Chromoting) component, as the vulnerable code path requires this component to be active and processing ETW events - disabling it removes the attack surface entirely, with the trade-off of losing remote desktop functionality. Restricting local user privileges to prevent untrusted users from running arbitrary code or generating crafted ETW events is an additional defense-in-depth measure, though it does not eliminate the vulnerability.
Same technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Low| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34742
GHSA-3xwm-4qrj-6qxr