How severe is GHSA-763j-3p5v-jfc6?

No CVSS score has been assigned to GHSA-763j-3p5v-jfc6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-763j-3p5v-jfc6?

GHSA-763j-3p5v-jfc6 affects the following packages: github.com/mvt-project/androidqf (Go). Ecosystems affected: Go.

How do I fix GHSA-763j-3p5v-jfc6?

Update github.com/mvt-project/androidqf to 1.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-763j-3p5v-jfc6 is resolved across your whole dependency graph.

How do I detect GHSA-763j-3p5v-jfc6 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mvt-project/androidqf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-763j-3p5v-jfc6 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-763j-3p5v-jfc6?

O3 pinpoints whether GHSA-763j-3p5v-jfc6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-763j-3p5v-jfc6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-763j-3p5v-jfc6 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-763j-3p5v-jfc6 published, and has it been updated?

GHSA-763j-3p5v-jfc6 was published on May 21, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-763j-3p5v-jfc6

androidqf: APK download Path Traversal in device APK paths

Also known asGO-2026-5206

Published

May 21, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐹github.com/mvt-project/androidqf

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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 additional vulnerability was independently identified by @0x0v1

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mvt-project/androidqf`	all versions	1.8.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mvt-project/androidqf. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/mvt-project/androidqf to 1.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-763j-3p5v-jfc6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-763j-3p5v-jfc6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-763j-3p5v-jfc6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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 containin

O3 Security · Impact-Aware SCA

Is GHSA-763j-3p5v-jfc6 in your dependencies?

O3 detects GHSA-763j-3p5v-jfc6 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works