# CVE-2026-46486: Mobile Verification Toolkit (MVT): Path Traversal via unsanitized File identifiers in iOS Backup processing

> An attacker can exploit path traversal in iOS backup processing to read or modify arbitrary files on the forensic analyst's system.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-5h3g-px23-w6vw, PYSEC-2026-2671

## What is CVE-2026-46486?

CVE-2026-46486 is a medium-severity path traversal vulnerability in mvt-project mvt, published on 8 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-46486?

3 open source packages ship an affected version, including mvt.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mvt` | PyPI | All versions | 2026.5.12 |
| `mvt` | PyPI | All versions | 2026.5.12 |
| `mvt` | PyPI | All versions | 2026.5.12 |

## How do I fix CVE-2026-46486?

Upgrade mvt to 2026.5.12 or later.

## Is CVE-2026-46486 being exploited?

There is no known exploitation of CVE-2026-46486 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46486 and fix it if it is affected.

What it is: CVE-2026-46486 is a medium-severity path traversal vulnerability in mvt-project mvt, published on 8 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-46486 in the wild and no public exploit code.

Affected packages and fixed versions:
- mvt (PyPI): affected all versions; fixed in 2026.5.12
- mvt (PyPI): affected all versions; fixed in 2026.5.12
- mvt (PyPI): affected all versions; fixed in 2026.5.12

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46486/ (Markdown: https://insights.sbomify.com/CVE-2026-46486/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46486
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46486
- OSV: https://osv.dev/vulnerability/CVE-2026-46486

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46486/
Summaries are generated and may contain mistakes; the official description above is the record.