Skip to main content
Vulnerability Database/CVE-2026-100852

CVE-2026-100852: AzuraCast Command Injection RCE Vulnerability

CVE-2026-100852 is a command injection flaw in AzuraCast that allows authenticated users to execute arbitrary commands through malicious usernames. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-100852 Overview

CVE-2026-100852 is a command injection vulnerability in AzuraCast before version 0.23.8. The flaw resides in the Liquidsoap configuration generator used for live recording. The generator fails to quote the streamer username passed into process.run calls. Authenticated station users holding Streamers and Profile permissions can set a username containing shell metacharacters. When a recording session closes, the injected payload executes as the Liquidsoap process user. The weakness is tracked under CWE-78 (OS Command Injection).

Critical Impact

Authenticated low-privilege station users can execute arbitrary commands on the AzuraCast host as the Liquidsoap process user, leading to compromise of the broadcasting server and any secrets it stores.

Affected Products

  • AzuraCast self-hosted web radio platform
  • All AzuraCast releases prior to 0.23.8
  • Deployments exposing station Streamers and Profile management to external users

Discovery Timeline

  • 2026-09-27 - CVE-2026-100852 published to the National Vulnerability Database
  • 2026-09-28 - Last updated in NVD database

Technical Details for CVE-2026-100852

Vulnerability Analysis

AzuraCast uses Liquidsoap to orchestrate live streaming and recording for broadcasting stations. When a streamer connects and later disconnects, AzuraCast generates a Liquidsoap configuration that invokes process.run to trigger post-recording actions. The generator concatenates the streamer's username into the shell command without applying Liquidsoap's string quoting or escaping functions.

An authenticated user with the Streamers and Profile permissions can edit their own streamer username through the station management UI. Setting that username to a value containing shell metacharacters such as backticks, $(), or ; causes the injected content to be interpreted by the shell when the recording closes. Execution occurs under the identity of the Liquidsoap process, which in default container deployments has broad access to AzuraCast media storage, configuration, and credentials.

Root Cause

The root cause is missing output encoding of user-controlled identifiers before they are embedded in a shell command string. The Liquidsoap config generator treats the username as trusted text rather than as data that must be quoted for a shell context. This is a textbook OS Command Injection pattern described by CWE-78.

Attack Vector

Exploitation requires an authenticated account with Streamers and Profile permissions on at least one station. The attacker updates the streamer username field to a payload containing shell metacharacters, then starts and ends a live broadcast to trigger the vulnerable process.run invocation. The payload runs on the server with the privileges of the Liquidsoap process. No user interaction from an administrator is required. Detailed advisory information is available in the AzuraCast GitHub Security Advisory GHSA-73rf-jp3g-8rcf and the VulnCheck Advisory.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-100852

Indicators of Compromise

  • Streamer or user profile records whose username contains shell metacharacters such as `, $(, ;, |, &, or newline characters.
  • Unexpected child processes spawned by the Liquidsoap process, especially shells (sh, bash), network utilities (curl, wget, nc), or interpreters (python, perl).
  • New or modified files in AzuraCast configuration, media, or web-accessible directories following a live recording session.
  • Outbound network connections from the AzuraCast or Liquidsoap container to unfamiliar hosts.

Detection Strategies

  • Review AzuraCast database tables and audit logs for streamer usernames containing non-alphanumeric characters beyond a short allow-list.
  • Monitor process ancestry on the AzuraCast host for Liquidsoap spawning shells or binaries outside its normal recording pipeline.
  • Correlate station live broadcast start and stop events with suspicious process execution timestamps.

Monitoring Recommendations

  • Enable verbose Liquidsoap and AzuraCast application logging and ship events to a centralized log platform for retention and search.
  • Alert on changes to the streamer profile endpoint, particularly updates that modify the username field.
  • Track egress traffic from AzuraCast hosts and containers, flagging any connections initiated by the Liquidsoap process.

How to Mitigate CVE-2026-100852

Immediate Actions Required

  • Upgrade AzuraCast to version 0.23.8 or later as the primary remediation.
  • Audit all station streamer accounts and remove or rename usernames that contain shell metacharacters.
  • Restrict the Streamers and Profile permissions to trusted operators only, and review existing role assignments.
  • Rotate credentials, API keys, and tokens stored on or accessible from the AzuraCast host if command execution is suspected.

Patch Information

The vulnerability is fixed in AzuraCast 0.23.8. The patch quotes the streamer username before it is embedded in the Liquidsoap process.run call, preventing shell interpretation of user-supplied characters. Refer to the AzuraCast GitHub Security Advisory GHSA-73rf-jp3g-8rcf for the official fix details and upgrade instructions.

Workarounds

  • Place the AzuraCast administrative interface behind a VPN or IP allow-list to limit who can authenticate and reach the vulnerable endpoint.
  • Enforce strict username validation at the reverse proxy or application layer, rejecting any input containing characters outside [A-Za-z0-9_-].
  • Run the Liquidsoap process under a dedicated, unprivileged account with read-only access to configuration and no outbound network access beyond what streaming requires.
bash
# Upgrade AzuraCast Docker deployment to a patched release
cd /var/azuracast
./docker.sh update-self
./docker.sh update

# Verify the running version is 0.23.8 or later
./docker.sh cli azuracast:setup --version

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.