← Back
CVE-2025-25295
Path Traversal in label-studio-sdk (CVE-2025-25295)
Summary
path traversal in label-studio-sdk (CVE-2025-25295). Risk of unauthorized operations or information disclosure. Exploitable via `GET /api/projects/1/export`. Mitigation: upgrade to `1.0.10` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-25295** has been found in label-studio-sdk.
Attackers can target a specific entry point like `GET /api/projects/1/export` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade label-studio-sdk to **1.0.10** or later.
If unsure, ask your IT team or search "label-studio-sdk CVE-2025-25295" on the vendor's site.
CVE-2025-25295 (label-studio-sdk) — CWE-22 /
Attack surface: GET /api/projects/1/export / `download` / `is_uploaded_file` / `is_local_file`
Patched: `1.0.10` — 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 label-studio-sdk. Attackers reach the vulnerable code path via `GET /api/projects/1/export` without authentication.
📍 Affected scope
label-studio-sdk — . Attack surface: GET /api/projects/1/export / `download` / `is_uploaded_file` / `is_local_file`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.0.10**.
🛡️ 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 /api/projects/1/export` requests with malformed payloads or SQL meta-characters. Run `grep -r 'label-studio-sdk' .` 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 'label-studio-sdk' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `label-studio-sdk` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /api/projects/1/export' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /api/projects/1/export` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade label-studio-sdk to 1.0.10ステージング環境で 1.0.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against GET /api/projects/1/export on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
label-studio-sdk
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.0.10"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-25295
- advisory https://github.com/advisories/GHSA-rgv9-w7jp-m23g
- package https://github.com/HumanSignal/label-studio-sdk
- package https://pypi.org/project/label-studio-sdk
- web https://github.com/HumanSignal/label-studio/security/advisories/GHSA-rgv9-w7jp-m23g
- web https://github.com/HumanSignal/label-studio-sdk/commit/4a9715c6b0b619371e89c09ea8d1c86ce5c880df