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

CVE-2026-100854: AzuraCast Authentication Bypass Flaw

CVE-2026-100854 is an authentication bypass vulnerability in AzuraCast affecting versions before 0.23.6. Attackers can inject metadata, disrupt broadcasts, and expose filesystem paths. This article covers technical details, affected versions, security impact, and mitigation strategies.

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-100854 Overview

CVE-2026-100854 affects AzuraCast versions before 0.23.6. The Liquidsoap API endpoint lacks the RequireInternalConnection middleware and derives the AutoDJ flag from header presence instead of a validated value. Authenticated users holding only the View station permission can inject arbitrary now-playing metadata, disrupt live broadcasts, and disclose filesystem paths. The flaw is categorized as Missing Authorization [CWE-862] and reflects a broken access control condition on an internal API that should not be reachable by low-privilege operators.

Critical Impact

Low-privileged station viewers can tamper with broadcast metadata, interrupt live streams, and leak server filesystem paths through an exposed internal API endpoint.

Affected Products

  • AzuraCast versions prior to 0.23.6
  • Deployments exposing the Liquidsoap API endpoint over the network
  • Multi-tenant AzuraCast instances granting the View station permission to untrusted users

Discovery Timeline

  • 2026-09-27 - CVE-2026-100854 published to the National Vulnerability Database (NVD)
  • 2026-09-30 - Last updated in NVD database

Technical Details for CVE-2026-100854

Vulnerability Analysis

AzuraCast exposes an internal Liquidsoap API that the broadcasting engine uses to signal track changes, request next songs, and update now-playing metadata. The endpoint is designed to be reachable only from the local Liquidsoap process. In versions before 0.23.6, the route is registered without the RequireInternalConnection middleware. Any authenticated user with the View station permission can invoke it over the network.

The handler compounds the problem by evaluating the AutoDJ indicator based on whether a specific HTTP header is present, rather than parsing and validating the header value. Attackers can toggle AutoDJ behavior simply by including the header in a crafted request. The combination of missing authorization and improper input evaluation enables metadata injection, broadcast disruption, and verbose error responses that disclose server paths.

Root Cause

Two defects coexist. First, the Liquidsoap API route is missing the authorization middleware that restricts access to internal callers. Second, the AutoDJ control flow checks for header existence instead of a validated boolean value, which breaks the intended trust boundary between external API clients and internal broadcast automation.

Attack Vector

Exploitation requires network access to the AzuraCast web interface and a valid account with the View station permission. The attacker sends HTTP requests to the Liquidsoap API endpoint, supplies arbitrary now-playing fields, and optionally injects the AutoDJ header to influence playback decisions. Error responses may return absolute filesystem paths, aiding reconnaissance for further attacks.

For technical specifics, see the GitHub Security Advisory GHSA-4fm3-ggg2-c6qx and the VulnCheck Advisory for AzuraCast.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-100854

Indicators of Compromise

  • Unexpected now-playing metadata changes that do not correlate with scheduled playlist entries or live DJ activity
  • HTTP requests from non-loopback addresses to the Liquidsoap API endpoint under /api/internal/
  • Application error logs containing absolute filesystem paths returned to View-permission users
  • Repeated AutoDJ state transitions triggered by requests originating from station viewer accounts

Detection Strategies

  • Audit AzuraCast web server access logs for requests to the Liquidsoap internal API from external source addresses
  • Correlate metadata update events against the user accounts and permission levels of the requesting principal
  • Flag any View station role invocations of endpoints that should be restricted to the Liquidsoap worker

Monitoring Recommendations

  • Forward AzuraCast and reverse-proxy logs into a centralized SIEM for continuous review
  • Alert on 5xx responses from the Liquidsoap API that include path strings in the response body
  • Baseline normal metadata update frequency per station and alert on deviations

How to Mitigate CVE-2026-100854

Immediate Actions Required

  • Upgrade AzuraCast to version 0.23.6 or later across all stations and worker nodes
  • Review and reduce the number of accounts holding the View station permission on sensitive stations
  • Rotate any API keys or session tokens issued to users whose activity cannot be fully audited
  • Inspect broadcast logs for unauthorized metadata changes during the exposure window

Patch Information

The maintainers addressed the issue in AzuraCast 0.23.6 by enforcing the RequireInternalConnection middleware on the Liquidsoap API endpoint and deriving the AutoDJ flag from a validated header value. Upgrade details are published in the GitHub Security Advisory GHSA-4fm3-ggg2-c6qx.

Workarounds

  • Restrict access to the Liquidsoap API endpoint at the reverse proxy, allowing only loopback or trusted internal addresses
  • Temporarily revoke the View station permission from untrusted users until the upgrade is complete
  • Disable verbose error output in the web server configuration to limit filesystem path disclosure
bash
# Example nginx snippet restricting the Liquidsoap internal API to loopback
location /api/internal/liquidsoap {
    allow 127.0.0.1;
    allow ::1;
    deny all;
    proxy_pass http://azuracast_backend;
}

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.