Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
AC:H for the heap-timing UAF and UI:R because the victim must actively install the malicious extension; PR:N as no prior authentication is needed, with full C/I/A impact from code execution.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Use after free in Extensions in Google Chrome prior to 150.0.7871.47 allowed an attacker who convinced a user to install a malicious extension to execute arbitrary code via a crafted Chrome Extension. (Chromium security severity: Critical)
AnalysisAI
Arbitrary code execution in Google Chrome desktop versions prior to 150.0.7871.47 stems from a use-after-free flaw in the Extensions component, which Chromium rated Critical severity. An attacker who convinces a victim to install a malicious extension can trigger the dangling-pointer condition through a crafted extension to run arbitrary code in the affected process. There is no public exploit identified at time of analysis, EPSS is low (0.16%, 6th percentile), and CISA/SSVC records no observed exploitation.
Technical ContextAI
The defect is a CWE-416 use-after-free in Chrome's Extensions subsystem, the C++ runtime that loads, sandboxes, and mediates the APIs available to browser extensions. Use-after-free occurs when code continues to reference a heap object after it has been freed; a crafted extension can drive Chrome into freeing an object while a pointer to it remains live, then reallocate that memory with attacker-controlled data to corrupt program state and hijack control flow. The CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* confirms the affected product is the Chrome browser application itself (all builds below the fixed release), and the Chromium 'Critical' label reflects the memory-corruption-to-code-execution potential typical of Extensions UAF bugs.
RemediationAI
Vendor-released patch: Chrome 150.0.7871.47 - upgrade all desktop Chrome installations to 150.0.7871.47 or later, which for most users occurs automatically; force the update via chrome://settings/help and restart the browser, then confirm the version. In managed environments, push the update through enterprise policy and verify rollout, per the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html). As a compensating control until patched, restrict extension installation using the ExtensionInstallBlocklist/ExtensionInstallAllowlist enterprise policies (allowlisting only vetted extensions) so users cannot side-load or install untrusted extensions - the trade-off is reduced user flexibility and added admin overhead in curating the allowlist. Auditing and removing unrecognized already-installed extensions further reduces exposure to the required attack precondition.
Same weakness CWE-416 – Use After Free
View allVendor StatusVendor
SUSE
Severity: Important| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-40460
GHSA-9q5x-c58m-xcp8