# Google Chrome use-after-free in Media Stream allows code execution

Published: 2026-06-09 · Severity: routine
Canonical: https://vorant.io/reports/a74b6cbd-a52c-5e09-b05c-6d3610b5a195/google-chrome-use-after-free-in-media-stream-allows-code-execution

> Use-after-free in Chrome Media Stream permits arbitrary code execution; patch to 138.0.7204.183/.184 immediately.

A use-after-free vulnerability in Google Chrome's Media Stream implementation permits arbitrary code execution in the context of the logged-on user. The flaw is tracked as CVE-2025-8292 and affects Chrome versions prior to 138.0.7204.183 on Windows and Mac, and prior to 138.0.7204.183 on Linux. Exploitation requires drive-by compromise—an attacker can trigger the flaw through a malicious web page or compromised site. The impact depends on user privilege level: non-administrative users face data theft and modification; administrative users face full system compromise including program installation and account creation. There is no evidence of active exploitation in the wild at publication.

Defenders should prioritize patching affected systems immediately after testing, enforce use of only fully supported and current browser versions, apply the principle of least privilege to limit account capabilities, and enable anti-exploitation features such as DEP or SIP where available. User education on untrusted links and social engineering remains critical, as drive-by compromise often depends on user navigation to malicious sites.

## Mentioned in this report

- Vulnerabilities: CVE-2025-8292

## Detection guidance (public sample)

### Chrome Browser Spawning Command Interpreter or LOLBin (Windows)

ATT&CK: T1189

Detects chrome.exe spawning a shell, script host or common LOLBin, which is a typical post-exploitation signal after a browser memory-corruption exploit such as a drive-by use-after-free. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.

```yaml
title: Chrome Browser Spawning Command Interpreter or LOLBin (Windows)
description: Detects chrome.exe spawning a shell, script host or common download/proxy-execution
  binary. Normal browsing does not launch these, so a hit may indicate renderer or
  browser exploitation (for example a drive-by use-after-free) leading to code execution
  as the logged-on user.
tags:
- attack.initial-access
- attack.t1189
- attack.execution
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    ParentImage|endswith: \chrome.exe
    Image|endswith:
    - \cmd.exe
    - \powershell.exe
    - \pwsh.exe
    - \wscript.exe
    - \cscript.exe
    - \mshta.exe
    - \rundll32.exe
    - \regsvr32.exe
    - \certutil.exe
    - \bitsadmin.exe
    - \msiexec.exe
  filter_native_messaging:
    CommandLine|contains: chrome-extension://
  condition: selection and not filter_native_messaging
falsepositives:
- Browser extensions or native messaging hosts that launch helper scripts through
  cmd.exe
- Enterprise web apps that use custom URL handlers launching scripts from Chrome
level: high
id: cdbeca9d-b4ee-5bfd-8d7c-9540b0e11b3a
status: experimental
author: Vorant
references:
- https://www.cisecurity.org/advisory/a-vulnerability-in-google-chrome-could-allow-for-arbitrary-code-execution_2025-068
```

### Chrome Browser Spawning Shell or Download Utility (Linux)

ATT&CK: T1189

Detects the Chrome process on Linux spawning a shell, scripting interpreter or download utility, which may indicate successful browser exploitation after a drive-by compromise. Auto-generated starting point — validate and tune in your environment before deploying. IOC matches can false-positive on shared infrastructure and decay as adversary infrastructure rotates.

```yaml
title: Chrome Browser Spawning Shell or Download Utility (Linux)
description: Detects a Chrome parent process spawning a shell, scripting interpreter
  or network utility on Linux. This is uncommon in normal browsing and may indicate
  code execution after exploiting a browser flaw via a malicious page.
tags:
- attack.initial-access
- attack.t1189
- attack.execution
logsource:
  category: process_creation
  product: linux
detection:
  selection:
    ParentImage|endswith:
    - /chrome
    - /google-chrome
    Image|endswith:
    - /bash
    - /sh
    - /dash
    - /zsh
    - /python
    - /python3
    - /perl
    - /curl
    - /wget
    - /nc
    - /ncat
  condition: selection
falsepositives:
- Wrapper launch scripts or desktop integration helpers started from Chrome through
  a shell
- Developers using browser-based tooling that invokes local scripts
level: medium
id: ca4fc784-6188-50ee-8da5-ca53790b4899
status: experimental
author: Vorant
references:
- https://www.cisecurity.org/advisory/a-vulnerability-in-google-chrome-could-allow-for-arbitrary-code-execution_2025-068
```

Behavioural rules are generated from public reporting — validate in your environment before deploying.

Source reporting: https://www.cisecurity.org/advisory/a-vulnerability-in-google-chrome-could-allow-for-arbitrary-code-execution_2025-068

---

This is the free public brief from Vorant Threat Intelligence. When citing, attribute "Vorant" and link https://vorant.io/reports/a74b6cbd-a52c-5e09-b05c-6d3610b5a195/google-chrome-use-after-free-in-media-stream-allows-code-execution.
In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), live profiles of the actors and CVEs it names, and the vendor research on the same campaign. Slack alerts fire on the vendors, sectors and countries a reader follows. A new account starts with three days of all of it, no card: https://vorant.io/signup