Quick answers
- Is CVE-2026-100849 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-100849 being exploited in the wild.
- How severe is CVE-2026-100849?
- 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-100849?
- 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-100849 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-100849?
- 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 AbstractConnector::getValidUrl() method in the webhook validation logic only blocks literal link-local IP addresses (169.254.0.0/16 and fe80::/10) while failing to reject loopback addresses, RFC1918 private ranges, and hostnames. Hostname resolution throws an exception that causes the validation check to be skipped entirely, allowing any hostname to bypass protections. An attacker with station-scoped WebHooks permission can exploit the PUT /station/{id}/webhook/{id}/test endpoint to trigger requests on demand against internal targets.
Affected products
- AzuraCast AzuraCast before 0.23.8
Timeline
- 2026-09-27: disclosed
- 2026-08-07: advisory: GitHub Security Advisory GHSA-3jp3-3wqw-jvw4 published