AzuraCast before 0.24.0 contains a server-side request forgery vulnerability that allows users with station WebHooks
Source GCVE Database
Not known to be exploited · CVSS 7.1 High : upgrade to 0.24.0 soon.
Data as of 8 Nov 2026, 18:03 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 7.1 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 6.5 |
- Patch
- Available – fixed in 0.24.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade AzuraCast to 0.24.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AzuraCastAzuraCast | Affected
| Fixed in
|
AI-suggested
A fix is available in AzuraCast version 0.24.0 and later. Users should upgrade to version 0.24.0 or newer to remediate this vulnerability. Since this is not a cloud service, manual patching is required. No other mitigation steps are indicated by the vendor advisory.
Description
AzuraCast versions before 0.24.0 have a server-side request forgery (SSRF) vulnerability that allows users with station WebHooks permission to bypass the UserUrlFilter SSRF protection via HTTP redirects. This enables attackers to configure certain webhooks (Mastodon, Telegram, GroupMe, RadioReg) to point to redirecting URLs, causing internal services to be accessed and their responses exposed in test logs.