MobSF is a mobile application security testing tool used. Prior to 4.5.1, find_icon_path_zip in mobsf/StaticAnalyzer/views/android/icon_analysis.py uses the Android manifest android:icon value to construct paths under the scan resource directory without rejecting traversal or verifying containment, allowing an authenticated user to upload a crafted ZIP or APK that reads a server file with an ALLOWED_EXTENSIONS suffix, copies it to DWD_DIR as the predictable name -icon., and retrieves it through the /download/ endpoint. The same behavior provides a file-existence oracle through the icon_path report field. This issue is fixed in version 4.5.1.
CVE-2026-68922
MEDIUMPre-NVD 5.55.5—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(medium)
- EG Risk
- 41(Track)EG Risk 41/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity55% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 29%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 19, 2026
Advisory Details (4)
Auto-updated Aug 18, 2026🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available
v4.5.1
Patch available: MobSF/Mobile-Security-Framework-MobSF v4.5.1
https://github.com/MobSF/Mobile-Security-Framework-MobSF/releases/tag/v4.5.1github_commit Patch Available
commit 62563ca429a7 (MobSF/Mobile-Security-Framework-MobSF)
Patch available: MobSF/Mobile-Security-Framework-MobSF v4.5.1 (contains commit 62563ca429a7)
https://github.com/MobSF/Mobile-Security-Framework-MobSF/commit/62563ca429a75b3e5d47a13b958e1d2e7d5e2bbfgithub_pr Patch Available
[HOTFIX][Security] Security Updates July 5 2026
Patch available: MobSF/Mobile-Security-Framework-MobSF v4.5.1 (PR #2627 merged 2026-07-05)
https://github.com/MobSF/Mobile-Security-Framework-MobSF/pull/2627github Patch Available🟡 PoC Available
Arbitrary File Read via Path Traversal in ZIP Uploads · Advisory · MobSF/Mobile-Security-Framework-MobSF · GitHub
https://github.com/MobSF/Mobile-Security-Framework-MobSF/security/advisories/GHSA-8j49-mmcx-4mp5Vendor Advisories for CVE-2026-68922(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| mobsf | 3.2.6 ... 4.4.5 (20 versions) | 4.5.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 17:13 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 16:26 UTCEG score recompute
- 2026-08-19 15:22 UTCEG score recompute
- 2026-08-18 18:22 UTCEG score recompute
- 2026-08-18 17:54 UTCEG score recompute
- 2026-08-18 17:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-68922?
CVE-2026-68922 is a medium vulnerability published on August 18, 2026. MobSF is a mobile application security testing tool used. Prior to 4.5.1, findiconpathzip in mobsf/StaticAnalyzer/views/android/iconanalysis.py uses the Android manifest android:icon value to construct paths under the scan resource directory without rejecting traversal or verifying containment,…
When was CVE-2026-68922 disclosed?
CVE-2026-68922 was first published in the National Vulnerability Database on August 18, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68922 actively exploited?
CVE-2026-68922 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 70.9% of all scored CVEs.
What is the CVSS score of CVE-2026-68922?
CVE-2026-68922 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-68922?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68922, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68922
Is Your Infrastructure Affected by CVE-2026-68922?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.