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

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

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

Google Chrome versions before 150.0.7871.47 contain an out-of-bounds memory read vulnerability that exposes sensitive in-process data when users open crafted webpages, affecting all Chrome…. A patch is available.

How to fix or mitigate EUVD-2026-40699?

24 hours: Inventory Chrome versions across all endpoints and identify systems running builds prior to 150.0.7871.47. 7 days: Deploy Chrome 150.0.7871.47 or later organization-wide via Microsoft Intune, Google Chrome Enterprise policies, or enterprise MSI distribution; verify 100% coverage of user-facing systems. 30 days: Audit deployment completion through endpoint telemetry; enforce policy to block execution of Chrome versions below 150.0.7871.47.

Google Chrome EUVD-2026-40699

| CVE-2026-14011 HIGH

Out-of-bounds Read (CWE-125)

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

GHSA-vr3h-9wm8-mcr4

Buffer Overflow Information Disclosure Google Red Hat Suse

8.1

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

8.1 HIGH

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

vuln.today AI

8.1 HIGH

Remote crafted page with user interaction (UI:R), no privileges; OOB read yields memory disclosure (C:H) and potential renderer crash (A:H), no integrity impact (I:N).

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

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

SUSE

HIGH

qualitative

Red Hat

6.5 MEDIUM

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 01, 2026 - 15:31 vuln.today

CVSS changed

Jul 01, 2026 - 15:22 NVD

8.1 (HIGH)

CVE Published

Jun 30, 2026 - 23:17 cve.org

HIGH 8.1

CVE Published

Jun 30, 2026 - 23:17 cve.org

UNKNOWN (no severity yet)

DescriptionCVE.org

Out of bounds read in SurfaceCapture in Google Chrome prior to 150.0.7871.47 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: Medium)

AnalysisAI

Out-of-bounds memory read in the SurfaceCapture component of Google Chrome before 150.0.7871.47 lets a remote attacker leak adjacent heap memory when a victim opens a crafted HTML page. Chromium rated the flaw Medium severity, though the associated CVSS is 8.1; there is no public exploit identified at time of analysis and EPSS estimates exploitation probability at just 0.17% (7th percentile), consistent with a browser bug fixed pre-disclosure. Successful exploitation could disclose sensitive in-process data or crash the renderer, and typically serves as one link in a larger sandbox-escape chain rather than standalone compromise.

Technical ContextAI

The defect is a CWE-125 out-of-bounds read within SurfaceCapture, the Chromium subsystem responsible for capturing rendered surfaces/frames (used by screen-capture, tab-capture, and compositor readback paths). When processing attacker-influenced dimensions or buffer offsets derived from a malicious page, the code reads beyond the bounds of an allocated buffer, returning memory that lies outside the intended region. Because this executes in the browser/renderer process handling untrusted web content, leaked bytes may include pointers or other process state useful for defeating ASLR. The affected product per EUVD/NVD is the Chrome desktop stable channel (cpe: Google Chrome) at all versions prior to 150.0.7871.47.

RemediationAI

Vendor-released patch: update Google Chrome to 150.0.7871.47 or later via the built-in updater (chrome://settings/help) and relaunch the browser; managed fleets should push the update through their enterprise deployment channel per the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html). Users of Chromium-based browsers should install the vendor build that incorporates the fixed Chromium base. As an interim compensating control before patching, restrict exposure to untrusted sites (enterprise browsing policies/allowlists) and, where feasible for high-risk users, disable or restrict screen/tab-capture and WebRTC capture APIs via enterprise policy - with the trade-off that legitimate screen-sharing and conferencing features will stop working. There is no need for network-level workarounds since the fix is a straightforward client update.