Skip to main content
VulnerabilityPublished

CVE-2026-68927: Mobile-Security-Framework-MobSF · Server-Side Request Forgery (SSRF)

Affects Mobile-Security-Framework-MobSFSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 3.0 Low : upgrade to 4.5.1 when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
3.0Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.5.1
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Mobile-Security-Framework-MobSF and mobsf/Mobile-Security-Framework-MobSF to 4.5.1.

Affected software

ProductAffectedFixed in
MobSFMobile-Security-Framework-MobSFAffected
  • <4.5.1
Fixed in
  • 4.5.1
GitHubmobsf/Mobile-Security-Framework-MobSFpkg:github/mobsf/Mobile-Security-Framework-MobSFOther threatsAffected
  • <4.5.1
Fixed in
  • 4.5.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in MobSF version 4.5.1. Users should upgrade to version 4.5.1 or later to remediate this issue. No other mitigation or workaround is indicated by the vendor advisory.

Description

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.

References

Community reviews

Loading reviews…