Quick answers
- Is CVE-2026-100848 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100848 being exploited in the wild.
- How severe is CVE-2026-100848?
- High severity, with a CVSS score of 7.1, published 27 September 2026.
- Which products and versions are affected?
- AzuraCast before 0.23.8.
- Is there a fix for CVE-2026-100848?
- 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-100848 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-100848?
- 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 server-side request forgery (SSRF) in the StationRemote::getUrlAsUri() and AbstractRemote::getNowPlayingAsync() code path. URL validation via Utilities\Urls::parseUserUrl() checks only HTTP/HTTPS scheme syntax and does not restrict loopback, RFC1918 private, link-local, or cloud-metadata IP ranges. A user holding the station-scoped RemoteRelays permission (not requiring full admin) can set a Remote Relay URL to an internal address, and the periodic background sync task will automatically and repeatedly fetch that URL, issuing unauthenticated HTTP requests to internal resources.
Affected products
- AzuraCast AzuraCast before 0.23.8
Timeline
- 2026-09-27: disclosed: Public advisory released
- 2026-07-31: other: Vulnerable code present in main branch as of commit bcf8754eef3a268ad82c3db4d81f7920c3c28b56