Quick answers
- Is CVE-2026-100854 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100854 being exploited in the wild.
- How severe is CVE-2026-100854?
- Medium severity, with a CVSS score of 6.3, published 27 September 2026.
- Which products and versions are affected?
- AzuraCast before 0.23.6.
- Is there a fix for CVE-2026-100854?
- A patch was published on 2026-04-23: Fix released in version 0.23.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100854 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-100854?
- 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 stems from two flaws: (1) missing RequireInternalConnection middleware on the /api/internal/{station_id}/liquidsoap/{action} endpoint, making it publicly accessible despite being internal-only; (2) the $asAutoDj flag is set based on the presence of the X-Liquidsoap-Api-Key header rather than validation of its value. A user with StationPermissions::View can exploit this over the network to invoke privileged Liquidsoap commands, bypassing authentication checks on FeedbackCommand, DjOffCommand, DjOnCommand, and CopyCommand. Version 0.23.6 patches both issues.
Affected products
- AzuraCast AzuraCast before 0.23.6
Timeline
- 2026-09-27: disclosed: Advisory published
- 2026-04-23: patched: Fix released in version 0.23.6