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