CVE-2026-121431

6.9 mediumEPSS 0.3%

Medium (6.9). EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

AzuraCast before 0.24.0 contains a server-side request forgery vulnerability that allows station users with WebHooks permission to bypass the UserUrlFilter guard via the Mastodon, Telegram, GroupMe, and RadioReg connectors. Attackers can set instance_url, api, or webhookurl to internal addresses and trigger the webhook test endpoint to reach loopback, private-network, or cloud-metadata services.

Severity

CVSS 4.0

6.9 medium

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L

CVSS 3.1

5.3 medium

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS: 0.3% estimated probability of exploitation activity in the next 30 days; 20th percentile. Scored 2026-11-04. A forecast for this CVE across the internet, not for your own systems.
CWE: CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10: A01:2025 Broken Access Control
Published: 2026-11-03 15:17 UTC
Modified: 2026-11-03 15:17 UTC
Record from: the NVD, synced 2026-11-03 15:46 UTC

Ask an AI about this CVE

ChatGPT Claude Google AI Mode

Show the prompt

Explain CVE-2026-121431 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121431?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121431?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-121431 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Versions

From the CNA's record in the CVE List.

Product	Affected
AzuraCast	before 0.24.0

Attack patterns (CAPEC)

CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stack JSON