CVE-2025-34090 Details
Description
Rejected reason: Neither filed by Chrome nor a valid security vulnerability.
A security bypass vulnerability has been identified in Google Chrome's AppBound cookie encryption mechanism. This issue arises from inadequate validation of COM server paths during inter-process communication. A local low-privileged attacker can exploit this vulnerability by hijacking the COM class identifier (CLSID) registration used by Chrome's elevation service, redirecting it to a non-existent or malicious binary. As a result, Chrome defaults to the older cookie encryption method, which is only protected by user-DPAPI. This flaw undermines the intended protections of the AppBound encryption design, allowing cookie decryption by any user-context malware without requiring SYSTEM-level access. While this vulnerability has been confirmed in Google Chrome with AppBound Encryption enabled, other Chromium-based browsers could be affected if they use similar COM-based encryption methods.
Google has acknowledged the vulnerability and is working on a fix. A partial solution is available but disabled by default. Users can also disable AppBound Encryption via Group Policy.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No CVSS 3.x data is available for this CVE.
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
No references are available for this CVE.
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
No affected product data is available for this CVE.
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 24, 2025 | CVE Rejected | [email protected] |
| Jul 24, 2025 | CVE Modified | [email protected] |
| Jul 2, 2025 | New CVE Received | [email protected] |