SSRF via unchecked android port assembly
Published Aug 18, 2026 · Updated Aug 18, 2026
SSRF in Mobile Security Framework (MobSF) before 4.5.1 allows remote authenticated users to reach internal services via a crafted APK. In get_browsable_activities in mobsf/StaticAnalyzer/views/android/manifest_analysis.py, MobSF validates only the android:host value with valid_host(), then appends a separate android:port when building the URL later fetched by _check_url(), so the final request bypasses the 80/443 port restriction. Exploitation requires the ability to upload or trigger analysis of a crafted APK and, for internal reachability, an attacker-controlled hostname with DNS rebinding; requests remain limited to /.well-known/assetlinks.json with redirects disabled.
Summary
What happened
SSRF in Mobile Security Framework (MobSF) before 4.5.1 allows remote authenticated users to reach internal services via a crafted APK. In get_browsable_activities in mobsf/StaticAnalyzer/views/android/manifest_analysis.py, MobSF validates only the android:host value with valid_host(), then appends a separate android:port when building the URL later fetched by _check_url(), so the final request bypasses the 80/443 port restriction. Exploitation requires the ability to upload or trigger analysis of a crafted APK and, for internal reachability, an attacker-controlled hostname with DNS rebinding; requests remain limited to /.well-known/assetlinks.json with redirects disabled.
The record
- CVE
- CVE-2026-68927
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- OpenSecurity
- Product
- Mobile Security Framework (MobSF)
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-95px-34x5-p37h reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo