{"answers":{"affected":"3 open source packages ship an affected version, including mvt.","exploited":"There is no known exploitation of CVE-2026-46486 in the wild and no public exploit code.","fix":"Upgrade mvt to 2026.5.12 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-46486 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-46486 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mvt (PyPI): affected all versions; fixed in 2026.5.12\n- mvt (PyPI): affected all versions; fixed in 2026.5.12\n- mvt (PyPI): affected all versions; fixed in 2026.5.12\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46486/ (Markdown: https://insights.sbomify.com/CVE-2026-46486/index.md)","id":"CVE-2026-46486","markdown":"https://insights.sbomify.com/CVE-2026-46486/index.md","name":"CVE-2026-46486","record":{"aliases":["GHSA-5h3g-px23-w6vw","PYSEC-2026-2671"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Mobile Verification Toolkit","requires_auth":"none","summary":"An attacker can exploit path traversal in iOS backup processing to read or modify arbitrary files on the forensic analyst's system.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Mobile Verification Toolkit (MVT): Path Traversal via unsanitized File identifiers in iOS Backup processing","id":"CVE-2026-46486","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"motionEye: Authentication possible via password hash","id":"CVE-2026-46488"},"packages":[{"ecosystem":"PyPI","fixed":["2026.5.12"],"introduced":["0"],"last_affected":[],"package":"mvt","purl":null,"source":"GHSA-5h3g-px23-w6vw"},{"ecosystem":"PyPI","fixed":["2026.5.12"],"introduced":["0"],"last_affected":[],"package":"mvt","purl":"pkg:pypi/mvt","source":"GHSA-5h3g-px23-w6vw"},{"ecosystem":"PyPI","fixed":["2026.5.12"],"introduced":["0"],"last_affected":[],"package":"mvt","purl":"pkg:pypi/mvt","source":"PYSEC-2026-2671"}],"prev":{"headline":"Dash: Users can write to config despire permissions (OIDC tested)","id":"CVE-2026-46485"},"products":["mvt"],"published":"2026-06-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-08","vendors":["mvt-project"]},"summary":"An attacker can exploit path traversal in iOS backup processing to read or modify arbitrary files on the forensic analyst's system.","url":"https://insights.sbomify.com/CVE-2026-46486/"}