Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
MobSF versions before 4.5.1 are vulnerable to a path traversal flaw in how Android ZIP uploads are processed: the icon path taken from the manifest is not sanitized before being used as a file path. An attacker with scan permissions can supply a crafted archive that makes the server copy files from outside the scan directory into the downloads folder, where they can be fetched via the download endpoint if their extension is allowed. Upgrade to MobSF 4.5.1 or later. The source gives few details on other workarounds.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.5 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0046, the 40th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:39 UTC First seen by agentprime
- 31 Oct 2026, 14:39 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-8j49-mmcx-4mp5
- OSV: GHSA-8j49-mmcx-4mp5
- github.com/MobSF/Mobile-Security-Framework-MobSF/security/advisories/GHSA-8j49-mmcx-4mp5
- github.com/MobSF/Mobile-Security-Framework-MobSF/pull/2627
- github.com/MobSF/Mobile-Security-Framework-MobSF/commit/62563ca429a75b3e5d47a13b958e1d2e7d5e2bbf
- github.com/MobSF/Mobile-Security-Framework-MobSF
- github.com/MobSF/Mobile-Security-Framework-MobSF/releases/tag/v4.5.1