MobSF Vulnerable to Arbitrary File Write (AR-Slip) via Absolute Path in .a Extraction
CVE-2025-58162GHSA-9gh8-9r95-3fc3
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (mobsf 4.4.1), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI mobsf
- Affected
- <= 4.4.0
- Fixed in
- 4.4.1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-9gh8-9r95-3fc3 lists affected ranges: PyPI mobsf >=0 <4.4.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-9gh8-9r95-3fc3 lists affected ranges: PyPI mobsf >=0 <=4.4.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
- EPSS
- CVE-2025-58162: 0.59% estimated exploitation activity in the next 30 days; percentile 48.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary The vulnerability allows any user to overwrite any files available under the account privileges of the running process. Details As part of static analysis, iOS MobSF supports loading and parsing statically linked libraries .a. When parsing such archives, the code extracts the embedded objects to the file system in the working directory of the analysis. The problem is that the current implementation does not prohibit absolute file names inside .a. If an archive item has a name like /abs/path/to/file, the resulting path is constructed as Path(dst) /name; for absolute paths, this leads to a complete substitution of the destination directory: writing occurs directly to the specified absolute directory. the path (outside the working directory). Thus, an authenticated user who uploaded a specially prepared .a, can write arbitrary files to any directory writable by the user of the MobSF process (for example, /tmp, neighboring directories inside ~/.MobSF, etc.). The key reason is…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-9gh8-9r95-3fc3
- Revision 1 · created ·
Published from osv record GHSA-9gh8-9r95-3fc3
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-58162 Advisory: MobSF Vulnerable to Arbitrary File Write (AR-Slip) via Absolute Path in .a Extraction IDs: CVE-2025-58162, GHSA-9gh8-9r95-3fc3 Record: https://patchnext.com/advisories/cve-2025-58162 (revision 2, source checked 26 Oct 2026, 13:35 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: mobsf 4.4.1. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI mobsf: affected <= 4.4.0; fixed in 4.4.1 ## Suggested inspection (read-only) - `python -m pip show mobsf`: prints the installed version. Run with the environment that serves production active. ## 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 mobsf. - 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://osv.dev/vulnerability/GHSA-9gh8-9r95-3fc3 (OSV record GHSA-9gh8-9r95-3fc3 lists affected ranges: PyPI mobsf >=0 <4.4.1 (fixed)) - Verified: https://github.com/advisories/GHSA-9gh8-9r95-3fc3 (GitHub-reviewed advisory GHSA-9gh8-9r95-3fc3 lists affected ranges: PyPI mobsf >=0 <=4.4.0) Commands are suggestions: review each one before running it.
Loading voting…