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-100856 Overview
CVE-2026-100856 is a code injection vulnerability in AzuraCast versions prior to 0.23.6. The flaw resides in the remote relay password field and stems from an incomplete migration from the vulnerable cleanUpString method to toRawString. Authenticated attackers holding the RemoteRelays station permission can inject nested Liquidsoap interpolation syntax. Successful exploitation executes arbitrary code inside the Liquidsoap process, exposes internal API keys, and disrupts station operation. The weakness is tracked as CWE-94: Improper Control of Generation of Code.
Critical Impact
Authenticated attackers can achieve arbitrary code execution in the Liquidsoap process and exfiltrate internal API keys from the AzuraCast host.
Affected Products
- AzuraCast versions before 0.23.6
- Deployments exposing the remote relay configuration to station-level users
- Any AzuraCast installation where users hold the RemoteRelays station permission
Discovery Timeline
- 2026-09-27 - CVE-2026-100856 published to the National Vulnerability Database
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-100856
Vulnerability Analysis
AzuraCast integrates with Liquidsoap, a scripting language used for audio stream processing. Configuration values supplied through the web interface are embedded into generated Liquidsoap scripts. The remote relay password field is one such value.
A prior fix replaced the cleanUpString sanitization routine with toRawString, which escapes characters that would otherwise break out of a Liquidsoap string literal. The migration was incomplete, and the remote relay password field continued to pass user input through the weaker sanitizer. Attackers can therefore embed Liquidsoap interpolation sequences that execute during script evaluation.
Because Liquidsoap runs with access to the broadcast process environment, injected code can read internal API keys, mutate station state, and interrupt live streams. The vulnerability requires authentication but no user interaction, and it is reachable over the network.
Root Cause
The root cause is improper neutralization of code syntax in a configuration field consumed by a downstream interpreter [CWE-94]. The cleanUpString method does not strip nested Liquidsoap interpolation markers, allowing user-controlled data to be parsed as code rather than as a string literal.
Attack Vector
An authenticated user with the RemoteRelays station permission submits a crafted password containing nested Liquidsoap interpolation syntax. When AzuraCast regenerates the Liquidsoap configuration and the daemon reloads, the injected expression evaluates inside the Liquidsoap process. The attacker gains code execution in that process context.
The vulnerability manifests when the remote relay password is persisted and the generated Liquidsoap script is loaded. See the GitHub Security Advisory GHSA-q4ph-8x8g-95f8 and the VulnCheck Advisory on AzuraCast 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-100856
Indicators of Compromise
- Remote relay password fields containing Liquidsoap interpolation markers such as #{...} or nested string delimiters.
- Unexpected outbound network connections initiated by the Liquidsoap process after a configuration reload.
- Unauthorized reads of AzuraCast internal API keys appearing in Liquidsoap logs or child processes.
- Station configuration changes applied by accounts holding only RemoteRelays permission.
Detection Strategies
- Audit AzuraCast database tables that store relay credentials for payloads containing Liquidsoap syntax characters.
- Monitor the Liquidsoap process for unexpected child processes, shell invocations, or network sockets.
- Enable AzuraCast administrative audit logging and alert on RemoteRelays configuration changes.
Monitoring Recommendations
- Forward AzuraCast and Liquidsoap logs to a centralized logging platform for correlation with process telemetry.
- Alert on any process spawned by liquidsoap that is not part of the known baseline.
- Review accounts with RemoteRelays permission and track their configuration write activity.
How to Mitigate CVE-2026-100856
Immediate Actions Required
- Upgrade AzuraCast to version 0.23.6 or later without delay.
- Revoke the RemoteRelays station permission from any account that does not require it.
- Rotate internal AzuraCast API keys that may have been exposed to the Liquidsoap process.
- Inspect existing relay configuration entries for payloads containing Liquidsoap interpolation syntax.
Patch Information
AzuraCast 0.23.6 completes the migration from cleanUpString to toRawString for the remote relay password field. Refer to the GitHub Security Advisory GHSA-q4ph-8x8g-95f8 for release details and commit references.
Workarounds
- Restrict the AzuraCast administrative interface to trusted networks using a reverse proxy or firewall.
- Temporarily disable remote relay functionality on stations until the upgrade is applied.
- Review and remove any suspicious relay password values from affected stations before upgrading.
# Configuration example: upgrade AzuraCast Docker deployment to a patched release
cd /var/azuracast
./docker.sh update
./docker.sh restart
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

