# CVE-2026-100850: AzuraCast before 0.23.8 SSRF and Local File Read via Remote Playlist

> Authenticated users can exploit SSRF and local file read via remote playlists to disclose sensitive host files and internal network data.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-r4xq-h58x-54m9, GHSA-rrjx-wrhf-8v47

## What is CVE-2026-100850?

CVE-2026-100850 is a medium-severity server-side request forgery vulnerability in AzuraCast, published on 27 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AzuraCast before 0.23.8 contains a server-side request forgery and local file read vulnerability in the AutoDJ remote playlist fetch (backend/src/Radio/AutoDJ/QueueBuilder.php, getMediaFromRemoteUrl()). A user with the station Media permission can create or update a playlist with source=remote_url and remote_type=playlist whose remote_url points at a file:// path or an internal/loopback/link-local HTTP endpoint. When AutoDJ builds the queue, the backend passes the user-supplied URL directly to file_get_contents() with no scheme allowlist and no private/loopback/metadata IP policy (PHP allow_url_fopen is enabled by default, including in the Docker image). Lines from the fetched resource are parsed as M3U/PLS entries, stored in StationQueue.autodj_custom_uri, and returned by GET /api/station/{station_id}/queue to any user with the Broadcasting permission, disclosing host files readable by the web container (for example /etc/passwd or the application .env) and the bodies of non-blind internal HTTP requests. No patched version was available at the time of publication.

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

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


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

No fix has been published for CVE-2026-100850 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-100850 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100850 is a medium-severity server-side request forgery vulnerability in AzuraCast, published on 27 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100850 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-100850/ (Markdown: https://insights.sbomify.com/CVE-2026-100850/index.md)
```

## Sources

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

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