CVE-2026-46486: Mobile Verification Toolkit (MVT) Path Traversal Vulnerability

MODERATE
Advisory Identifier: GHSA-5h3g-px23-w6vw
CWE-22
Published
Advisory Summary

CVE-2026-46486 is a MODERATE path traversal vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting Mobile Verification Toolkit (MVT) libraries in the PyPI ecosystem. The issue involves path traversal via unsanitized file identifiers in ios backup processing. Remediation is available by upgrading affected packages to version 2026.5.12.

CVE-2026-46486 at a Glance

CVE Identifier CVE-2026-46486
GHSA Identifier GHSA-5h3g-px23-w6vw
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Affected Product Mobile Verification Toolkit (MVT)
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix CVE-2026-46486

To remediate this vulnerability, upgrade all affected Mobile Verification Toolkit (MVT) dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

mvt fixed: 2026.5.12
pip install mvt>=2026.5.12
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show mvt

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-46486, inspect your installed packages using pip:

pip show mvt

Analyze the terminal output to locate any version of Mobile Verification Toolkit (MVT) in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2026.5.12), your application is affected.

Note: The pip show mvt command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In Mobile Verification Toolkit (MVT), software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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`): `file_id` is used to construct both read source and write destination paths. Traversal sequences in `file_id` cause decrypted content to be written to an arbitrary location on the analyst's filesystem. - **`mvt-ios check-backup`** (via `_get_backup_file_from_id()` 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 assessed as Moderate because exploitation requires a specifically crafted malicious bundle to be parsed by the analyst. There are trust mitigations between stakeholders involved in the handoff of the sample that reduce the likelihood of this scenario. **File read (check-backup):** An adversary can force MVT to open and parse files outside the backup directory. Practical exploitation is reduced as it requires the attacker to know or guess the analyst’s directory layout for cross-case targeting, and the traversed file from the host must be a valid SQLite database or plist whose schema matches what the specific MVT module expects. ### Patched version [2026.5.12](https://github.com/mvt-project/mvt/releases/tag/v2026.5.12) ### Credits This issue was identified during a security assessment conducted by 0xche.

CVE-2026-46486 Affected Mobile Verification Toolkit (MVT) Versions

1 component(s)
Fixed Versions:
2026.5.12
Product / Package Ecosystem Affected Versions Fixed Version
mvt
PyPI
< 2026.5.12
2026.5.12

References

Frequently Asked Questions

What is CVE-2026-46486?
CVE-2026-46486 is a security vulnerability in Mobile Verification Toolkit (MVT) involving Path Traversal via unsanitized File identifiers in iOS Backup processing under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal').
Which Mobile Verification Toolkit (MVT) versions are affected?
Affected versions include releases prior to 2026.5.12 across affected packages: mvt.
What version fixes CVE-2026-46486?
Upgrading to 2026.5.12 (or the latest patched release for your respective branch) resolves the vulnerability.
Is mvt affected?
Yes, mvt is affected in releases prior to 2026.5.12. Upgrade your dependency to 2026.5.12 or later.
What CWE is associated with CVE-2026-46486?
CVE-2026-46486 is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.).
How can I check PyPI dependencies for CVE-2026-46486?
Run the dependency tree command: 'pip show mvt'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-5h3g-px23-w6vw",
  "modified" : "2026-06-09T13:12:24Z",
  "published" : "2026-05-21T17:05:29Z",
  "aliases" : [ "CVE-2026-46486" ],
  "summary" : "Mobile Verification Toolkit (MVT): Path Traversal via unsanitized File identifiers in iOS Backup processing",
  "details" : "### Summary\n\nThe `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:\n\n- **`mvt-ios decrypt-backup`** (`decrypt.py`): `file_id` is used to construct both read source and write destination paths. Traversal sequences in `file_id` cause decrypted content to be written to an arbitrary location on the analyst's filesystem.\n- **`mvt-ios check-backup`** (via `_get_backup_file_from_id()` 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.\n\n### Impact\n\n**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 assessed as Moderate because exploitation requires a specifically crafted malicious bundle to be parsed by the\nanalyst. There are trust mitigations between stakeholders involved in the handoff of the sample that reduce the likelihood of this scenario.\n\n**File read (check-backup):** An adversary can force MVT to open and parse files outside the backup directory. Practical exploitation is reduced as it requires the attacker to know or guess the analyst’s directory layout for cross-case targeting, and the traversed file from the host must be a valid SQLite database or plist whose schema matches what the specific MVT module expects.\n\n### Patched version\n[2026.5.12](https://github.com/mvt-project/mvt/releases/tag/v2026.5.12)\n\n### Credits\nThis issue was identified during a security assessment conducted by 0xche.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "mvt"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2026.5.12"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 2026.4.28"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/mvt-project/mvt/security/advisories/GHSA-5h3g-px23-w6vw"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-46486"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/mvt-project/mvt"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mvt-project/mvt/releases/tag/v2026.5.12"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-22" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-21T17:05:29Z",
    "nvd_published_at" : "2026-06-08T19:16:45Z"
  }
}