← Back
CVE-2026-42606
high
CVSS 8.1
Vulnerability in azuracast/azuracast (CVE-2026-42606)
Summary
vulnerability in azuracast/azuracast (CVE-2026-42606). Confidential information can be exposed externally. Exploitable via ``ApplyXForwarded``. Mitigation: upgrade to `0.23.6` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42606** has been found in azuracast/azuracast.
Attackers can target a specific entry point like ``ApplyXForwarded`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/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-42606" on the vendor's site.
CVE-2026-42606 (azuracast/azuracast) — CWE-640 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `ApplyXForwarded` / `fastcgi_pass` / `proxy_params.conf` / `proxy_pass`
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
**A vulnerability** (CWE-640) exists in azuracast/azuracast. Attackers reach the vulnerable code path via ``ApplyXForwarded`` without authentication.
📍 Affected scope
azuracast/azuracast — . Attack surface: `ApplyXForwarded` / `fastcgi_pass` / `proxy_params.conf` / `proxy_pass`.
🔥 Severity
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally
🔧 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 request patterns matching this CVE's known IOCs. Run `grep -r 'azuracast/azuracast' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'azuracast/azuracast' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `azuracast/azuracast` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade azuracast/azuracast to 0.23.6ステージング環境で 0.23.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
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"}]}]