What is the CVSS score of CVE-2026-11096?

CVE-2026-11096 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Is there a patch available for CVE-2026-11096?

Yes, a patch is available for CVE-2026-11096. Update the affected software to the latest version immediately.

Google Chrome CVE-2026-11096

EUVD-2026-34558 MEDIUM

Out-of-bounds Read (CWE-125)

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

GHSA-8486-5w5v-m2fj

Information Disclosure Google Buffer Overflow Chrome

6.5

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

6.5 MEDIUM

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

SUSE

MEDIUM

qualitative

Red Hat

6.5 MEDIUM

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 05, 2026 - 17:31 vuln.today

CVSS changed

Jun 05, 2026 - 17:22 NVD

6.5 (MEDIUM)

CVE Published

Jun 04, 2026 - 23:17 nvd

UNKNOWN (no severity yet)

CVE Published

Jun 04, 2026 - 23:17 nvd

MEDIUM 6.5

DescriptionCVE.org

Out of bounds read in WebRTC in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)

AnalysisAI

Out-of-bounds read in the WebRTC component of Google Chrome prior to 149.0.7827.53 exposes potentially sensitive process memory contents to remote attackers. Exploitation requires no authentication (CVSS PR:N) but does require user interaction - a victim must visit a specially crafted HTML page (CVSS UI:R). The confidentiality impact is rated High (C:H) with no integrity or availability consequence, meaning a successful attack leaks memory contents rather than enabling code execution. No public exploit identified at time of analysis, and EPSS at 0.03% (10th percentile) reflects low observed exploitation probability.

Technical ContextAI

WebRTC (Web Real-Time Communication) is a built-in browser framework in Chrome that handles peer-to-peer audio, video, and data streaming, processing complex binary protocol data including RTP/RTCP packets and SDP negotiation payloads. CWE-125 (Out-of-Bounds Read) describes a class of memory safety errors where code reads beyond the allocated buffer boundary, typically due to insufficient bounds checking on attacker-influenced length or index values. In a browser context, this means the renderer process may read and potentially disclose adjacent heap or stack memory - which could contain residual sensitive data such as credentials, session tokens, or other page content previously processed by the same process. The affected versions are confirmed as all Chrome desktop releases prior to 149.0.7827.53, per EUVD-2026-34558 and the Google Chrome Releases advisory.

RemediationAI

Update Google Chrome to version 149.0.7827.53 or later, which contains the vendor-released patch for this vulnerability. The official advisory and update instructions are available at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Chrome typically auto-updates, but administrators managing enterprise deployments should verify the update has been applied via policy or endpoint management tooling. If immediate patching is not possible, a compensating control is to restrict or disable WebRTC via enterprise policy (Chrome policy 'WebRtcAllowed' set to false), though this will break WebRTC-dependent functionality such as video conferencing applications. An alternative compensating control is to enforce Safe Browsing and URL filtering to reduce the attack surface by preventing access to unknown or untrusted external sites where a malicious HTML page could be hosted.