Mobile Verification Toolkit (MVT): Path Traversal via unsanitized File identifiers in iOS Backup processing
CVE-2026-46486GHSA-5h3g-px23-w6vw
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (mvt 2026.5.12), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI mvt
- Affected
- <= 2026.4.28
- Fixed in
- 2026.5.12
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-5h3g-px23-w6vw lists affected ranges: PyPI mvt >=0 <2026.5.12 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-5h3g-px23-w6vw lists affected ranges: PyPI mvt >=0 <=2026.4.28
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2026-46486: 0.38% estimated exploitation activity in the next 30 days; percentile 31.66 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary The fileID field from Manifest.db (a SQLite database inside iOS backups, generated by the device) is used directly in filesystem path construction without validation. This affects two commands through a shared code path: - mvt-ios decrypt-backup (decrypt.py): fileid is used to construct both read source and write destination paths. Traversal sequences in fileid cause decrypted content to be written to an arbitrary location on the analyst's filesystem. - mvt-ios check-backup (via getbackupfilefromid() in ios/modules/base.py): the same unvalidated fileID resolves to files outside the backup directory, which are then opened and parsed. Parsed contents flow into JSON results and CSV timeline. Impact File write (decrypt-backup): An adversary delivering a crafted iOS backup can cause attacker controlled content to be written to arbitrary paths writable by the analyst process. This could be leveraged for code execution via shell profile modification or SSH key injection. Severity is…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-5h3g-px23-w6vw
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-5h3g-px23-w6vw
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-46486 Advisory: Mobile Verification Toolkit (MVT): Path Traversal via unsanitized File identifiers in iOS Backup processing IDs: CVE-2026-46486, GHSA-5h3g-px23-w6vw Record: https://patchnext.com/advisories/cve-2026-46486 (revision 3, source checked 26 Oct 2026, 13:45 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: mvt 2026.5.12. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI mvt: affected <= 2026.4.28; fixed in 2026.5.12 ## Suggested inspection (read-only) - `python -m pip show mvt`: prints the installed version. Run with the environment that serves production active. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on mvt. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-5h3g-px23-w6vw (OSV record GHSA-5h3g-px23-w6vw lists affected ranges: PyPI mvt >=0 <2026.5.12 (fixed)) - Verified: https://github.com/advisories/GHSA-5h3g-px23-w6vw (GitHub-reviewed advisory GHSA-5h3g-px23-w6vw lists affected ranges: PyPI mvt >=0 <=2026.4.28) Commands are suggestions: review each one before running it.
Loading voting…