Path Traversal in mvt (CVE-2026-46486)
Summary
Path traversal in mvt (CVE-2026-46486). Risk of unauthorized operations or information disclosure. Exploitable via fileID. Mitigation: upgrade to 2026.5.12 or later.
Original description
The description as published by the source.
MVT (Mobile Verification Toolkit) helps with conducting forensics of mobile devices in order to find signs of a potential compromise. Prior to version 2026.5.12, there is a path traversal vulnerability via unsanitized File identifiers in iOS Backup processing. This issue has been patched in version 2026.5.12.
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-46486 has been found in mvt.
Attackers can target a specific entry point like fileID over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade mvt to 2026.5.12 or later.
If unsure, ask your IT team or search "mvt CVE-2026-46486" on the vendor's site.
CVE-2026-46486 (mvt) — CWE-22
Attack surface: fileID / Manifest.db / decrypt.py / file_id
Patched: 2026.5.12 — 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.
Path traversal (CWE-22) exists in mvt. Attackers reach the vulnerable code path via fileID.
Check the vendor advisory for the affected versions of mvt. Attack surface: fileID / Manifest.db / decrypt.py / file_id.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2026.5.12.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mvt' . 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 'mvt' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mvtを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mvt to 2026.5.12ステージング環境で 2026.5.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com