Mobile Security Framework (MobSF) has a SSRF Vulnerability fix bypass on assetlinks_check with DNS Rebinding

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.4 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:L

EPSS

• CVE-2025-31116: 0.48% estimated exploitation activity in the next 30 days; percentile 41.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The latest deployed fix for the SSRF vulnerability is through the use of the call validhost(). The code available at lines /ae34f7c055aa64fca58e995b70bc7f19da6ca33a/mobsf/MobSF/utils.py#L907-L957 is vulnerable to SSRF abuse using DNS rebinding technique. PoC The following proof of concept: Yields : Which generate an initlal random url that leverages dns rebinding after 1 time host resolution and remains to that IP for 30 seconds. As you can notice the initial resolution was pointing to 1.1.1.1. The second time the IP was resolved to 127.0.0.1. Such an attack could be adjusted for other IP addresses. Impact The usual impact of Server-side request forgery. Remediation - Avoid the use of socket.gethostbyname() since it issues and DNS query.

Published by the source

31 Mar 2025, 17:23 UTC

Last modified by the source

10 Jun 2026, 17:14 UTC

Source last checked

26 Oct 2026, 13:32 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-fcfq-m8p6-gw56

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-fcfq-m8p6-gw56

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-31116

Advisory: Mobile Security Framework (MobSF) has a SSRF Vulnerability fix bypass on assetlinks_check with DNS Rebinding
IDs: CVE-2025-31116, GHSA-fcfq-m8p6-gw56
Record: https://patchnext.com/advisories/cve-2025-31116 (revision 2, source checked 26 Oct 2026, 13:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mobsf 4.3.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mobsf: affected < 4.3.2; fixed in 4.3.2

## Suggested inspection (read-only)
- `python -m pip show mobsf`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mobsf.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-fcfq-m8p6-gw56 (OSV record GHSA-fcfq-m8p6-gw56 lists affected ranges: PyPI mobsf >=0 <4.3.2 (fixed))
- Verified: https://github.com/advisories/GHSA-fcfq-m8p6-gw56 (GitHub-reviewed advisory GHSA-fcfq-m8p6-gw56 lists affected ranges: PyPI mobsf >=0 <4.3.2)

Commands are suggestions: review each one before running it.