Categories
CVE-2026-42605 high CVSS 8.8

Path Traversal in azuracast/azuracast (CVE-2026-42605)

Summary

Path traversal in azuracast/azuracast (CVE-2026-42605). Successful exploitation can lead to full system takeover. Exploitable via POST /api/station/{station_id}/files/upload. Mitigation: upgrade to 0.23.6 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-42605 has been found in azuracast/azuracast.
Attackers can target a specific entry point like POST /api/station/{station_id}/files/upload over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade azuracast/azuracast to 0.23.6 or later.
If unsure, ask your IT team or search "azuracast/azuracast CVE-2026-42605" on the vendor's site.

CVE-2026-42605 (azuracast/azuracast) — CWE-22 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/station/{station_id}/files/upload / currentDirectory / finally / CannotProcessMediaException
Patched: 0.23.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in azuracast/azuracast. Attackers reach the vulnerable code path via POST /api/station/{station_id}/files/upload.

📍 Affected scope

Check the vendor advisory for the affected versions of azuracast/azuracast. Attack surface: POST /api/station/{station_id}/files/upload / currentDirectory / finally / CannotProcessMediaException.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 0.23.6.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/station/{station_id}/files/upload requests with malformed payloads or SQL meta-characters. Run grep -r 'azuracast/azuracast' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'azuracast/azuracast' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で azuracast/azuracast を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'POST /api/station/{station_id}/files/upload' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/station/{station_id}/files/upload への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade azuracast/azuracast to 0.23.6

    ステージング環境で 0.23.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against POST /api/station/{station_id}/files/upload on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

composer azuracast/azuracast
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.23.6"}]}]
Packagist azuracast/azuracast
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.23.6"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details