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-100857 Overview
CVE-2026-100857 is a code injection vulnerability in AzuraCast before version 0.23.4. The flaw resides in the ConfigWriter::cleanUpString() method, which fails to sanitize Liquidsoap string interpolation sequences. Authenticated users with Media or Profile permissions can inject arbitrary Liquidsoap code into station configuration. Attackers embed #{process.run()} expressions in playlist URLs or station metadata fields. These expressions execute shell commands as the azuracast user when the station restarts. The vulnerability is classified under [CWE-94] Improper Control of Generation of Code.
Critical Impact
Authenticated attackers achieve remote code execution on the AzuraCast host as the azuracast user, compromising station data and the underlying server.
Affected Products
- AzuraCast versions prior to 0.23.4
- AzuraCast self-hosted radio broadcasting platform
- Deployments using Liquidsoap-based station configurations
Discovery Timeline
- 2026-09-27 - CVE-2026-100857 published to NVD
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-100857
Vulnerability Analysis
AzuraCast generates Liquidsoap configuration files to control audio streaming for each station. The ConfigWriter::cleanUpString() method prepares user-supplied strings for inclusion in these configuration files. The method escapes certain characters but does not strip or neutralize Liquidsoap string interpolation sequences of the form #{...}.
Liquidsoap evaluates #{expression} sequences inside double-quoted strings at runtime. When AzuraCast writes attacker-controlled values into the configuration and the station restarts, Liquidsoap evaluates the injected expression. The process.run() function then invokes a shell with attacker-chosen arguments. Commands run under the identity of the azuracast service account.
Exploitation requires authenticated access with Media or Profile permissions, a low privilege bar in multi-user AzuraCast deployments. Successful exploitation yields host-level command execution, enabling data theft, lateral movement, or persistence on the broadcasting server.
Root Cause
The root cause is insufficient output encoding when generating Liquidsoap configuration. cleanUpString() treats the Liquidsoap string grammar incompletely, omitting the interpolation metacharacter sequence #{. Any field written through this sanitizer inherits the injection flaw.
Attack Vector
An authenticated attacker submits a crafted value into a field that reaches the Liquidsoap configuration generator, such as a playlist URL or station metadata string. The attacker embeds a payload resembling #{process.run("<command>")} within the submitted value. When the station restarts, Liquidsoap parses the configuration, evaluates the interpolation sequence, and executes the embedded command as the azuracast user. Refer to the GitHub Security Advisory GHSA-93fx-5qgc-wr38 and the VulnCheck Advisory on AzuraCast RCE for additional technical context.
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 AttemptsDetection Methods for CVE-2026-100857
Indicators of Compromise
- Presence of #{ or #{process.run substrings inside generated Liquidsoap configuration files on the AzuraCast host.
- Unexpected child processes spawned by Liquidsoap or the azuracast user, such as sh, bash, curl, or wget.
- Playlist URLs or station metadata fields in the AzuraCast database containing Liquidsoap interpolation syntax.
Detection Strategies
- Audit AzuraCast station configuration records for any field containing #{ sequences.
- Monitor the Liquidsoap process tree for shell invocations or network tooling that is not part of normal broadcasting operations.
- Review web application logs for authenticated requests from Media or Profile role users modifying playlist URLs or metadata with unusual characters.
Monitoring Recommendations
- Enable process creation logging on the AzuraCast host and alert on child processes of Liquidsoap.
- Forward AzuraCast application logs and host process telemetry to a centralized analytics platform for correlation.
- Track station restart events and correlate them with recent configuration changes made by low-privilege user roles.
How to Mitigate CVE-2026-100857
Immediate Actions Required
- Upgrade AzuraCast to version 0.23.4 or later, which contains the patched ConfigWriter::cleanUpString() implementation.
- Review existing station configurations and user-submitted fields for Liquidsoap interpolation payloads and remove them.
- Rotate credentials and inspect the azuracast user environment for persistence artifacts if exploitation is suspected.
Patch Information
The fix is included in AzuraCast 0.23.4. The upstream project addresses the sanitization gap in ConfigWriter::cleanUpString() so that Liquidsoap interpolation sequences are neutralized before configuration generation. See the GitHub Security Advisory GHSA-93fx-5qgc-wr38 for release details.
Workarounds
- Restrict Media and Profile role assignments to trusted operators until the patch is applied.
- Manually inspect and sanitize playlist URLs and station metadata fields to remove any #{...} sequences before station restarts.
- Isolate the AzuraCast container or host at the network layer to limit the blast radius of command execution by the azuracast user.
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

