CVE-2026-76836 AzuraCast CVE debrief

Who should care

Defenders responsible for AzuraCast systems, especially those with station managers holding profile permissions, should assess their exposure and prioritize remediation accordingly.

Why it matters

CVE-2026-76836 allows station managers with profile permissions to write Liquidsoap configuration, potentially leading to execution of arbitrary operating system commands. Defenders should verify exposure, assess impact, and prioritize remediation.

• Potential execution of arbitrary operating system commands by station managers with profile permissions.
• Bypass of intended permission boundaries for Liquidsoap configuration.
• Possible impact on the security and integrity of the AzuraCast system and its data.
• Need for verification of affected versions and remediation from official sources.

Technical summary

The AzuraCast application exposes Liquidsoap custom configuration fields through an endpoint that lacks permission guarding. Specifically, the PUT /api/station/{station_id}/profile/edit endpoint deserializes with the GROUP_GENERAL annotation while requiring only StationPermissions::Profile. This allows station managers with only profile permissions to write configuration that is typically reserved for broadcasting operators. The configuration is then emitted into the generated Liquidsoap .liq script, which can execute operating system commands via process.run() and process.exec() when the backend restarts.

Defensive priority

Defenders should prioritize verifying exposure and assessing the impact of this vulnerability on their systems, especially those with station managers holding profile permissions.

Recommended defensive actions

• Verify the exposure of AzuraCast systems to this vulnerability, especially those with station managers holding profile permissions.
• Assess the impact of this vulnerability on the systems and prioritize remediation accordingly.
• Restrict access to the PUT /api/station/{station_id}/profile/edit endpoint to only authorized personnel.
• Monitor for any suspicious activity related to this vulnerability.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and source references provide details on the vulnerable endpoint and the potential impact of exploitation. However, the corpus does not establish versions, exploitation, impact, or remediation, which require verification from the supplied official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.