androidqf: APK download Path Traversal in device APK paths

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

1.1 · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary During device acquisition, getPathToLocalCopy() constructs local filesystem paths for downloaded APKs using a filename component extracted by extractFileName(). The extraction splits on ==/ and takes the remainder without sanitization. If a compromised device returns a crafted APK path containing traversal sequences, filepath.Join resolves them, allowing the file to be written outside the intended apks/ directory. Practical exploitability is limited because Android enforces strict package path formats under /data/app/ and does not allow apps to register paths containing traversal sequences. Rated Informational as a defense-in-depth concern. Impact An attacker with control of the connected device could potentially write files outside the expected output directory on the acquisition workstation, leading to arbitrary file overwrite with attacker-controlled content. Patched version 1.8.3 Credits - This issue was identified during a security assessment conducted by 0xche. - An…

Published by the source

21 May 2026, 17:11 UTC

Last modified by the source

21 May 2026, 17:12 UTC

Source last checked

26 Oct 2026, 15:22 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-763j-3p5v-jfc6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-763j-3p5v-jfc6

Advisory: androidqf: APK download Path Traversal in device APK paths
IDs: GHSA-763j-3p5v-jfc6
Record: https://patchnext.com/advisories/ghsa-763j-3p5v-jfc6 (revision 1, source checked 26 Oct 2026, 15:22 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 1.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/mvt-project/androidqf 1.8.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/mvt-project/androidqf: affected <= 1.8.2; fixed in 1.8.3

## Suggested inspection (read-only)
- Go github.com/mvt-project/androidqf: check the installed version with your package manager.

## 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 github.com/mvt-project/androidqf.
- 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://github.com/advisories/GHSA-763j-3p5v-jfc6 (GitHub-reviewed advisory GHSA-763j-3p5v-jfc6 lists affected ranges: Go github.com/mvt-project/androidqf >=0 <=1.8.2)

Commands are suggestions: review each one before running it.