Internet radio operators using AzuraCast have a new security update to assess. The project’s 0.24.1 changelog, dated November 19, 2026, lists tighter handling of metadata sent to its Liquidsoap playback engine, restrictions on cross-station playlist assignments and stronger permission checks for broadcasting settings.

The changes matter particularly where several stations, volunteers or clients share one installation. The underlying advisories describe ways that users with limited station permissions could reach functions beyond their assigned roles.

Why station permissions matter

A November 5 project advisory describes a flaw through which a user with station media permissions could use specially crafted track metadata to cause operating-system commands to run inside the Liquidsoap container during playback. The advisory rates the issue high severity. It does not establish a takeover of the underlying host.

A separate advisory describes station profile users being able to read or change Icecast and SHOUTcast passwords despite lacking broadcasting permissions. Its stated risks include unauthorized broadcasting and locking legitimate operators out.

These are authenticated-user scenarios: the relevant permissions are part of the attack prerequisites. That makes delegated access an important operational issue for hosting companies and multi-user stations.

What the release notes confirm

The 0.24.1 notes say users can assign only playlists belonging to the station they manage. They also require broadcasting permission for the station-profile sections controlling broadcasting, alongside improved security for annotated values sent to Liquidsoap. The project’s official container package listing identifies 0.24.1 as available.

There is a documentation caveat. When checked November 21, the two original advisory pages still listed no patched version, while the newer changelog described the related protections. RNN has not independently tested the fixes or verified attacks against operating stations.

For operators, the practical next step is to confirm the deployed version with their administrator or hosting provider, review the current update notes and check who holds media, profile and broadcasting permissions. These checks help protect control of the stream and separation between users.