How severe is GHSA-jf2q-463c-6f52?

No CVSS score has been assigned to GHSA-jf2q-463c-6f52 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jf2q-463c-6f52?

GHSA-jf2q-463c-6f52 affects the following packages: github.com/mvt-project/androidqf (Go). Ecosystems affected: Go.

How do I fix GHSA-jf2q-463c-6f52?

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-jf2q-463c-6f52 is resolved across your whole dependency graph.

How do I detect GHSA-jf2q-463c-6f52 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-jf2q-463c-6f52 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-jf2q-463c-6f52 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jf2q-463c-6f52 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-jf2q-463c-6f52 published, and has it been updated?

GHSA-jf2q-463c-6f52 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

Not in CISA KEV

GHSA-jf2q-463c-6f52 — androidqf

GHSA-jf2q-463c-6f52 is a security vulnerability in github.com/mvt-project/androidqf. A fix is available for github.com/mvt-project/androidqf — see the affected versions and patch details below.

androidqf: Zip entry Name Injection in APK bundle (Zip Slip for zip consumers)

Also known asGO-2026-5464

Published

May 21, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

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

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.

Impact

A 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.

Patched version

1.8.3

Credits

This issue was identified during a security assessment conducted by 0xche.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mvt-project/androidqf`	all versions	1.8.3`go get github.com/mvt-project/androidqf@v1.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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-jf2q-463c-6f52 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Summary `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. ### Impact A compromised device could inject path traversal sequences into the acquisition bundle's zip entry names. When a forensic analyst or forensic tooling extrac

O3 Security · Impact-Aware SCA

Is GHSA-jf2q-463c-6f52 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works