Is CVE-2026-76836 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-76836 being exploited in the wild.

How severe is CVE-2026-76836?

High severity, with a CVSS score of 8.8, published 24 August 2026.

Is there a fix for CVE-2026-76836?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-76836 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-76836?

Check whether you run AzuraCast at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-76836: AzuraCast privilege escalation via Liquidsoap custom configuration

CVE-2026-76836 · Severity: high · CVSS 8.8 · Published 2026-08-24

AzuraCast is a self-hosted web radio management platform. A flaw in the profile editing API allows station managers with limited permissions to modify Liquidsoap audio backend configuration fields that should be restricted to broadcasting operators. Attackers can inject arbitrary commands into the Liquidsoap script, which executes them as the backend process when the service restarts, potentially compromising the entire radio station system.

Technologies: AzuraCast. Vendors: AzuraCast.

Quick answers

Is CVE-2026-76836 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-76836 being exploited in the wild.
How severe is CVE-2026-76836?: High severity, with a CVSS score of 8.8, published 24 August 2026.
Which products and versions are affected?: AzuraCast before 0.23.8.
Is there a fix for CVE-2026-76836?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-76836 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-76836?: Check whether you run AzuraCast at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a privilege escalation via insufficient authorization checks in the profile editing endpoint. The backend_config property in Station.php is annotated with GROUP_GENERAL, and the PUT /api/station/{station_id}/profile/edit endpoint deserializes user input with that group while requiring only StationPermissions::Profile permission. AbstractArrayEntity::fromArray() assigns all public properties without field-level permission validation, making custom_config_top, custom_config, custom_config_pre_playlists, custom_config_pre_live, custom_config_pre_fade, and custom_config_bottom writable by an attacker. ConfigWriter::writeCustomConfigurationSection() emits these values verbatim into the Liquidsoap .liq script where process.run() and process.exec() execute OS commands when the backend restarts (triggered automatically via the sync task). The dedicated /api/station/{id}/liquidsoap-config endpoint correctly requires StationPermissions::Broadcasting, but the profile endpoint bypasses this intended access control boundary.

Affected products

AzuraCast AzuraCast before 0.23.8

Timeline

2026-08-24: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.