# CVE-2026-42605: AzuraCast: Path Traversal in `currentDirectory` Parameter Enables Remote Code Execution via Media Upload

> Authenticated users can exploit path traversal in media uploads to write arbitrary files, enabling remote code execution on AzuraCast installations.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2026
- **Updated:** 11 May 2026
- **Also known as:** GHSA-vp2f-cqqp-478j

## What is CVE-2026-42605?

CVE-2026-42605 is a high-severity path traversal vulnerability in AzuraCast, published on 9 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

AzuraCast is a self-hosted, all-in-one web radio management suite. Prior to version 0.23.6, the currentDirectory request parameter in the Flow.js media upload endpoint (POST /api/station/{station_id}/files/upload) is not sanitized for path traversal sequences. When combined with a local filesystem storage backend (the default), an authenticated user with media management permissions can write arbitrary files outside the station's media storage directory, achieving remote code execution by writing a PHP webshell to the web root. This issue has been patched in version 0.23.6.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

2 open source packages ship an affected version, including azuracast/azuracast. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `azuracast/azuracast` | Packagist | All versions | 0.23.6 |
| `azuracast/azuracast` | Packagist | All versions | 0.23.6 |

Products: Azuracast Azuracast.

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

Upgrade azuracast/azuracast to 0.23.6 or later.

## Is CVE-2026-42605 being exploited?

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

## Other vulnerabilities in AzuraCast

- [CVE-2026-42606](https://insights.sbomify.com/CVE-2026-42606/): AzuraCast: Password Reset Poisoning via Untrusted X-Forwarded-Host Header Leads to Account Takeover and 2FA Bypass (high 8.1)
- [CVE-2023-2531](https://insights.sbomify.com/CVE-2023-2531/): Improper Restriction of Excessive Authentication Attempts in azuracast/azuracast (high 7.3)
- [CVE-2023-2191](https://insights.sbomify.com/CVE-2023-2191/): Cross-site Scripting (XSS) - Stored in azuracast/azuracast (low 3.5)
- [CVE-2025-67737](https://insights.sbomify.com/CVE-2025-67737/): AzuraCast Vulnerable to Pre-Auth File Deletion & Admin RCE (low 3.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42605 is a high-severity path traversal vulnerability in AzuraCast, published on 9 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42605 exists.

Affected packages and fixed versions:
- azuracast/azuracast (Packagist): affected all versions; fixed in 0.23.6
- azuracast/azuracast (Packagist): affected all versions; fixed in 0.23.6

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-42605/ (Markdown: https://insights.sbomify.com/CVE-2026-42605/index.md)
```

## Sources

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

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