{"answers":{"affected":"3 open source packages ship an affected version, including github.com/mvt-project/androidqf.","exploited":"There is no known exploitation of GHSA-jf2q-463c-6f52 in the wild and no public exploit code.","fix":"Upgrade github.com/mvt-project/androidqf to 1.8.3 or later.","what":"GHSA-jf2q-463c-6f52 is a path traversal vulnerability in github.com/mvt-project/androidqf, published on 21 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for GHSA-jf2q-463c-6f52 and fix it if it is affected.\n\nWhat it is: GHSA-jf2q-463c-6f52 is a path traversal vulnerability in github.com/mvt-project/androidqf, published on 21 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of GHSA-jf2q-463c-6f52 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/mvt-project/androidqf (Go): affected all versions; fixed in 1.8.3\n- github.com/mvt-project/androidqf (Go): affected all versions; fixed in 1.8.3\n- github.com/mvt-project/androidqf (Go): affected all versions; fixed in 1.8.3\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/GHSA-jf2q-463c-6f52/ (Markdown: https://insights.sbomify.com/GHSA-jf2q-463c-6f52/index.md)","id":"GHSA-jf2q-463c-6f52","markdown":"https://insights.sbomify.com/GHSA-jf2q-463c-6f52/index.md","name":"GHSA-jf2q-463c-6f52","record":{"aliases":["GO-2026-5464"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Android forensic tool","requires_auth":"none","summary":"A compromised Android device can inject path traversal sequences into forensic acquisition bundles, allowing arbitrary file writes when extracted by vulnerable tools.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\n`generateZipPath()` constructs zip entry names for collected APKs using device controlled content from `extractFileName()`. Since `extractFileName()` does not reject traversal sequences, the resulting zip entry name can contain `../`. AndroidQF itself does not extract the zip it creates, but any forensic tool that extracts the acquisition bundle without zip-slip protection could write files to attacker chosen paths.\n\n### Impact\nA compromised device could inject path traversal sequences into the acquisition bundle's zip entry names. When a forensic analyst or forensic tooling extracts the bundle without entry name validation, files could be written outside the intended extraction directory.\n\n### Patched version\n[1.8.3](https://github.com/mvt-project/androidqf/releases/tag/v1.8.3)\n\n### Credits\nThis issue was identified during a security assessment conducted by 0xche.","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"androidqf: Zip entry Name Injection in APK bundle (Zip Slip for zip consumers)","id":"GHSA-jf2q-463c-6f52","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["1.8.3"],"introduced":["0"],"last_affected":[],"package":"github.com/mvt-project/androidqf","purl":null,"source":"GHSA-jf2q-463c-6f52"},{"ecosystem":"Go","fixed":["1.8.3"],"introduced":["0"],"last_affected":[],"package":"github.com/mvt-project/androidqf","purl":"pkg:golang/github.com/mvt-project/androidqf","source":"GHSA-jf2q-463c-6f52"},{"ecosystem":"Go","fixed":["1.8.3"],"introduced":["0"],"last_affected":[],"package":"github.com/mvt-project/androidqf","purl":"pkg:golang/github.com/mvt-project/androidqf","source":"GO-2026-5464"}],"products":null,"published":"2026-05-21","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A compromised Android device can inject path traversal sequences into forensic acquisition bundles, allowing arbitrary file writes when extracted by vulnerable tools.","url":"https://insights.sbomify.com/GHSA-jf2q-463c-6f52/"}