Vulnerability in mobsf (CVE-2026-68924)
Summary
Vulnerability in mobsf (CVE-2026-68924). Risk of unauthorized operations or information disclosure. Exploitable via ZIP_MAX_UNCOMPRESSED_FILE_SIZE. Mitigation: upgrade to 4.5.1 or later.
Original description
The description as published by the source.
MobSF is a mobile application security testing tool used. Prior to 4.5.1, the unzip function in mobsf/StaticAnalyzer/views/common/shared_func.py logs that an archive member exceeding ZIP_MAX_UNCOMPRESSED_FILE_SIZE is being skipped but does not continue to the next member, so an authenticated user can upload a crafted ZIP or APK whose oversized member is extracted to disk when the aggregate ZIP_MAX_UNCOMPRESSED_TOTAL_SIZE limit has not yet been reached, potentially exhausting disk space and preventing further scans. This issue is fixed in version 4.5.1.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-68924 has been found in mobsf.
Attackers can target a specific entry point like ZIP_MAX_UNCOMPRESSED_FILE_SIZE over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.9/10.
What to do: upgrade mobsf to 4.5.1 or later.
If unsure, ask your IT team or search "mobsf CVE-2026-68924" on the vendor's site.
CVE-2026-68924 (mobsf) — CWE-400 / CVSS v3 4.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ZIP_MAX_UNCOMPRESSED_FILE_SIZE / continue / shared_func.py / break
Patched: 4.5.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in mobsf. Attackers reach the vulnerable code path via ZIP_MAX_UNCOMPRESSED_FILE_SIZE.
Check the vendor advisory for the affected versions of mobsf. Attack surface: ZIP_MAX_UNCOMPRESSED_FILE_SIZE / continue / shared_func.py / break.
Severity: Medium (CVSS 4.9/10). Risk of unauthorized operations or information disclosure.
Update to 4.5.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mobsf' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mobsf' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mobsfを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mobsf to 4.5.1ステージング環境で 4.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- patch github.com
- patch github.com
- web github.com