# CVE-2026-121431: AzuraCast before 0.24.0 SSRF Filter Bypass via Webhook Connectors


- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-8x7j-92r4-99vr, GHSA-qh22-76gf-qwc4

## What is CVE-2026-121431?

CVE-2026-121431 is a medium-severity vulnerability in AzuraCast, published on 3 Nov 2026. 

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-121431?


## How do I fix CVE-2026-121431?

Upgrade AzuraCast to 0.24.0 or later. The advisory says that version fixes it.

## Is CVE-2026-121431 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121431 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121431 and fix it if it is affected.

What it is: CVE-2026-121431 is a medium-severity vulnerability in AzuraCast, published on 3 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121431 exists.

Affected product: AzuraCast. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121431/ (Markdown: https://insights.sbomify.com/CVE-2026-121431/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121431
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121431
- OSV: https://osv.dev/vulnerability/CVE-2026-121431

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121431/
Summaries are generated and may contain mistakes; the official description above is the record.
