SSRF (Server-Side Request Forgery) in mobsf (CVE-2026-68927)
Summary
SSRF in mobsf (CVE-2026-68927). Risk of unauthorized operations or information disclosure. Exploitable via rebind.example. 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, get_browsable_activities in mobsf/StaticAnalyzer/views/android/manifest_analysis.py validates only an Android manifest android:host value with valid_host before appending a separately supplied android:port to the URL fetched by _check_url, allowing an authenticated user to upload a crafted APK that makes requests to an attacker-selected nonstandard port at /.well-known/assetlinks.json. With an attacker-controlled hostname and DNS rebinding between validation and the requests.get connection, the request can reach an internal service, although redirects remain disabled and the path is fixed. 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-68927 has been found in mobsf.
Attackers can target a specific entry point like rebind.example over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.0/10.
What to do: upgrade mobsf to 4.5.1 or later.
If unsure, ask your IT team or search "mobsf CVE-2026-68927" on the vendor's site.
CVE-2026-68927 (mobsf) — CWE-918 / CVSS v3 3.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: rebind.example / c_url
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.
SSRF (CWE-918) exists in mobsf. Attackers reach the vulnerable code path via rebind.example.
Check the vendor advisory for the affected versions of mobsf. Attack surface: rebind.example / c_url.
Severity: Low (CVSS 3.0/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