Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-10108 high CVSS 7.5

Path Traversal in xiaomusic (CVE-2026-10108)

Summary

Path traversal in xiaomusic (CVE-2026-10108). Confidential information can be exposed externally. Exploitable via GET /music/{file_path. Mitigation: upgrade to 0.5.8 or later.

Original description

The description as published by the source.

xiaomusic v0.5.7 contains an unauthenticated path traversal vulnerability in the GET /music/{file_path:path} endpoint that allows unauthenticated attackers to read arbitrary files outside the intended music directory by exploiting an incomplete path prefix check. Attackers can request files from sibling directories whose names share the music_path prefix by crafting traversal sequences, bypassing the path restriction due to the missing trailing separator in the comparison logic to retrieve arbitrary files from the server.

Source: GitHub Security Advisories (Global) 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-10108 has been found in xiaomusic.
Attackers can target a specific entry point like GET /music/{file_path over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade xiaomusic to 0.5.8 or later.
If unsure, ask your IT team or search "xiaomusic CVE-2026-10108" on the vendor's site.

CVE-2026-10108 (xiaomusic) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /music/{file_path
Patched: 0.5.8 — 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 xiaomusic. Attackers reach the vulnerable code path via GET /music/{file_path without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of xiaomusic. Attack surface: GET /music/{file_path.

🔥 Severity

Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.5.8.

🛡️ 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 GET /music/{file_path requests with malformed payloads or SQL meta-characters. Run grep -r 'xiaomusic' . 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 'xiaomusic' . | grep -v node_modules

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

  2. 2
    Hunt for indicators of compromise detect 
    grep 'GET /music/{file_path' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 3
    Apply patch patch 
    Upgrade xiaomusic to 0.5.8

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

  4. 4
    Post-deployment verification verify 
    Replay attack against GET /music/{file_path on staging to confirm patch closes the vector

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

Affected packages

pip xiaomusic
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.8"}]}]
PyPI xiaomusic
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.5.8"}]}]

References

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