What is the CVSS score of EUVD-2026-40513?

EUVD-2026-40513 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Google Chrome are affected by EUVD-2026-40513?

Google Chrome's Updater component on macOS (versions prior to 150.0.7871.47) contains a use-after-free vulnerability enabling local privilege escalation.. A patch is available.

How to fix or mitigate EUVD-2026-40513?

Within 24 hours: Notify macOS users and security teams; assess current Chrome version distribution. Within 7 days: Deploy Chrome 150.0.7871.47 or later to all macOS systems via auto-update, MDM, or manual distribution. Within 30 days: Verify 100% patch coverage on macOS fleet; review system logs for unusual privilege escalation attempts targeting the Chrome Updater process.

Google Chrome EUVD-2026-40513

| CVE-2026-13827 HIGH

Use After Free (CWE-416)

2026-06-30 chrome-cve-admin@google.com

GHSA-73hh-x7p5-j6ff

Privilege Escalation Denial Of Service Google Use After Free Memory Corruption Red Hat Suse

7.8

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

7.8 HIGH

AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

vuln.today AI

7.8 HIGH

Local attack via a malicious file (AV:L) needing a user/updater trigger (UI:R) but no prior privileges (PR:N); successful escalation grants total C/I/A impact within an unchanged scope.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

4.0 AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

SUSE

HIGH

qualitative

Red Hat

8.2 HIGH

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 01, 2026 - 16:33 vuln.today

CVSS changed

Jul 01, 2026 - 14:22 NVD

7.8 (HIGH)

CVE Published

Jun 30, 2026 - 23:16 cve.org

UNKNOWN (no severity yet)

CVE Published

Jun 30, 2026 - 23:16 cve.org

HIGH 7.8

DescriptionCVE.org

Use after free in Updater in Google Chrome on Mac prior to 150.0.7871.47 allowed a local attacker to perform privilege escalation via a malicious file. (Chromium security severity: High)

AnalysisAI

Local privilege escalation in Google Chrome's Updater component on macOS versions prior to 150.0.7871.47 lets an attacker abuse a use-after-free (CWE-416) via a malicious file to gain the elevated privileges under which the updater runs. Google rates the Chromium severity as High, and the CVSS 3.1 base score is 7.8; there is no public exploit identified at time of analysis and it is not listed in CISA KEV. EPSS is low at 0.13% (3rd percentile), consistent with the SSVC exploitation status of 'none'.

Technical ContextAI

The flaw sits in the Chrome Updater on macOS - the background component (historically the GoogleSoftwareUpdate/Keystone-derived tooling) responsible for fetching and installing browser updates, typically with elevated system privileges so it can write into protected application locations. The root cause is CWE-416 (Use After Free): a memory region is freed but a dangling reference is subsequently dereferenced, allowing an attacker who controls surrounding heap state via a crafted malicious file to manipulate freed-then-reused memory. Because the vulnerable code path executes in a higher-privileged updater context, corrupting that memory can redirect execution or file operations to the attacker's benefit. The CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* identifies Google Chrome as the affected application, with the defect specific to the macOS build of its updater.

RemediationAI

Vendor-released patch: update Google Chrome on macOS to 150.0.7871.47 or later, as published in Google's Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html); Chrome's own auto-updater will normally deliver this, and users can force it via chrome://settings/help followed by a relaunch. In managed fleets, push the updated build through MDM/enterprise policy and confirm the installed version to ensure the vulnerable updater code is replaced. Because exploitation requires a local attacker to place and trigger a malicious file, interim compensating controls are to restrict local/interactive access to Mac endpoints, enforce least privilege on local accounts, and use endpoint protection to detect unauthorized files dropped into Chrome/updater directories - these reduce opportunity but do not remove the flaw, so upgrading remains the definitive fix.