CVE-2026-10975

chromium-browser: Use after free in WebRTC

Published Jun 4, 2026 CVSS 3.1 · 8.8 High EPSS < 1% KEV · Not listed
Description
Use after free in WebRTC in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

Analysis

AI-generated

Technical impact

A use‑after‑free vulnerability in the WebRTC component of Google Chrome, identified as a CWE‑416 flaw, allows a remote attacker to execute arbitrary code within the browser’s sandbox by serving a specially crafted HTML page. The flaw also exhibits characteristics of a memory misuse defect (CWE‑825) where a freed object is accessed again, enabling the attacker to control execution flow inside the protected sandbox, thus potentially compromising confidentiality, integrity, and availability of the user’s system. The described problem carries a Chromium security severity of High.

Affected Systems

Google Chrome is affected in all releases prior to 149.0.7827.53. Users running version 149.0.7827.52 or earlier should be aware that any WebRTC traffic generated by a malicious web page could trigger the use‑after‑free exploit. The risk is confined to browsers that process the vulnerable WebRTC sandbox code.

Risk and Exploitability

The EPSS score is 0.00071, indicating a very low but nonzero exploitation probability, and the vulnerability is not listed in CISA’s Known Exploited Vulnerabilities catalog, but the nature of the flaw – remote code execution through a crafted HTML page – makes it attractive to attackers. If a user opens a malicious page that triggers the exploit, an attacker can take control of the browser process. Updating to a fixed release stops the vulnerability, while an attacker would need to exploit the older code path to succeed.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Google Chrome to the latest stable release (149.0.7827.53 or newer).
  • Disable WebRTC functionality by setting the chrome experimental flag ‑‑disable-webrtc or through group policy to prevent any WebRTC traffic from reaching the browser.
  • Ensure browsers are regularly updated and only allow trusted websites to access WebRTC features through content security policy configurations.

Generated by OpenCVE AI on June 7, 2026 at 14:34 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-6325-1 chromium security update
History
Type Values Removed Values Added
Title Use‑after‑free in WebRTC Enables Sandbox Escape in Chrome chromium-browser: Use after free in WebRTC
Weaknesses CWE-825
References
Metrics threat_severity

None

threat_severity

Important

Type Values Removed Values Added
First Time appeared Apple
Apple macos
Linux
Linux linux Kernel
Microsoft
Microsoft windows
CPEs cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
cpe:2.3:o:apple:macos:-:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:-:*:*:*:*:*:*:*
cpe:2.3:o:microsoft:windows:-:*:*:*:*:*:*:*
Vendors & Products Apple
Apple macos
Linux
Linux linux Kernel
Microsoft
Microsoft windows
Type Values Removed Values Added
Title Use‑after‑free in WebRTC Enables Sandbox Escape in Chrome
Type Values Removed Values Added
First Time appeared Google
Google chrome
Vendors & Products Google
Google chrome
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 8.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Use after free in WebRTC in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Weaknesses CWE-416
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Chrome
Published
Updated
Jun 6, 2026, 3:56 AM
Reserved
Jun 4, 2026, 5:06 PM
Status
Analyzed
Published
Jun 4, 2026, 11:17 PM
Modified
Jul 22, 2026, 8:10 PM
Severity
Important
Public date
Jun 2, 2026, 12:00 AM