Quick answers
- Is CVE-2026-100855 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100855 being exploited in the wild.
- How severe is CVE-2026-100855?
- Medium severity, with a CVSS score of 6.5, published 27 September 2026.
- Which products and versions are affected?
- AzuraCast before 0.23.6.
- Is there a fix for CVE-2026-100855?
- A patch was published on 2026: version 0.23.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-100855 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-100855?
- 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 GET /api/station/{station_id}/file/{id}/play endpoint in AzuraCast backend/config/routes/api_station.php is missing the Middleware\Permissions check that protects adjacent endpoints in the same /file/{id} route group. While RequireLogin middleware verifies the user is authenticated, it does not validate station-level permissions; the controller's call to mediaRepo->requireForStation() only checks media-station association, not authorization. Media IDs are auto-increment integers, enabling trivial sequential enumeration of the entire media library.
Affected products
- AzuraCast AzuraCast before 0.23.6
Timeline
- 2026-04-23: disclosed
- 2026: patched: version 0.23.6