Information Disclosure in AzuraCast (CVE-2026-100851)
Summary
Vulnerability in AzuraCast (CVE-2026-100851). Confidential information can be exposed externally. Exploitable via GET /api/station/{id}/vue/profile.
Original description
The description as published by the source.
AzuraCast before 0.23.8 contains a broken access control vulnerability in the GET /api/station/{id}/vue/profile endpoint that allows authenticated users with only View Station Page permission to read Icecast/Shoutcast admin, source, and relay passwords. Attackers with View-only access can call this endpoint and receive plaintext frontend credentials in the JSON response, then use the admin password to authenticate to the Icecast admin interface without Broadcasting permission.
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-100851 has been found in AzuraCast.
Attackers can target a specific entry point like GET /api/station/{id}/vue/profile over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.6/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "AzuraCast CVE-2026-100851" on the vendor's site.
CVE-2026-100851 (AzuraCast) — CWE-200 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/station/{id}/vue/profile
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.
Information disclosure (CWE-200) exists in AzuraCast. Attackers reach the vulnerable code path via GET /api/station/{id}/vue/profile.
Check the vendor advisory for the affected versions of AzuraCast. Attack surface: GET /api/station/{id}/vue/profile.
Severity: High (CVSS 7.6/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/station/{id}/vue/profile requests with malformed payloads or SQL meta-characters. Run grep -r '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
-
1Identify exposure identify
grep -r 'AzuraCast' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
AzuraCastを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/station/{id}/vue/profile' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/station/{id}/vue/profileへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /api/station/{id}/vue/profile on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com
- web vulncheck.com
- web nvd.nist.gov
- web github.com