VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

mobsf: vulnerability history, versions and safety

mobsf is a package in the PyPI ecosystem. Vulert records 43 vulnerabilities for it across 23 releases, from Oct 2022 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
43 vulnerabilities recorded H8 M11 L2 U22
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
24 in the last 12 months

Most recent disclosure 19 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mobsf vulnerabilities

Vulert verdict on mobsf 4.5.3 i

Updated on 22 Oct 2026

Careful: 4.5.3 has 3 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 58/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 4.5.3 — affected i
  • Vulnerabilities on record 43 over 3 years · 24 in the last year i
  • Latest disclosure 19 Aug 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Stars 21,966 i
  • OpenSSF scorecard 6/10 i
  • Last release 1 month ago i
  • Licence GPL-3.0-only i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for mobsf, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.5.3 21 Sep 2026 M1 U2 GPL-3.0-only No Details →
4.5.2 10 Aug 2026 M1 U2 GPL-3.0-only No Details →
4.5.1 06 Jul 2026 M1 U2 GPL-3.0-only No Details →
4.4.5 26 Jan 2026 M4 L1 U5 GPL-3.0-only Yes Details →
4.4.2 31 Aug 2025 H1 M4 L1 U6 GPL-3.0-only Yes Details →
4.4.0 31 Aug 2025 H1 M5 L2 U8 GPL-3.0-only Yes Details →
4.3.2 29 Mar 2025 H1 M7 L2 U10 GPL-3.0-only No Details →
4.3.0 24 Jan 2025 H4 M8 L2 U14 GPL-3.0-only No Details →
4.1.3 05 Nov 2024 H4 M9 L2 U15 GPL-3.0-only No Details →
3.9.7 25 Mar 2024 H5 M11 L2 U18 GPL-3.0-only No Details →
3.7.6 28 Aug 2023 H7 M11 L2 U21 GPL-3.0-only No Details →
3.6.9 23 Jul 2023 H7 M11 L2 U21 GPL-3.0 No Details →
3.6.0 04 Oct 2022 H7 M11 L2 U21 GPL-3.0 No Details →
3.5.0 23 Jan 2022 H7 M11 L2 U21 GPL-3.0 No Details →
3.4.6 08 Jan 2022 H7 M11 L2 U21 GPL-3.0 No Details →
3.4.3 25 Apr 2021 H7 M11 L2 U21 GPL-3.0 No Details →
3.4.0 28 Mar 2021 H7 M11 L2 U21 GPL-3.0 No Details →
3.3.5 22 Mar 2021 H7 M11 L2 U21 GPL-3.0 No Details →
3.3.3 08 Mar 2021 H7 M11 L2 U21 GPL-3.0 No Details →
3.2.9 20 Jan 2021 H7 M11 L2 U21 GPL-3.0 No Details →
3.2.8 20 Jan 2021 H7 M11 L2 U21 GPL-3.0 No Details →
3.2.7 17 Jan 2021 H7 M11 L2 U21 GPL-3.0 No Details →
3.2.6 17 Jan 2021 H7 M11 L2 U21 GPL-3.0 No Details →

All 23 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 2
  • 2024 6
  • 2025 10
  • 2026 24

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 24 of the 43 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for mobsf

The 5 most severe of 43 vulnerabilities recorded for this package

Search all 43 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-31116: MobSF Vulnerability in DNS Rebinding Leading to SSRF 9.8 critical 4b8bab5a9858c69fe13be4631b82d82186e0d3bd 31 Mar 2025
CVE-2026-24490: MobSF Stored XSS Vulnerability via Manifest Analysis 8.1 high 4.4.5 26 Jan 2026
CVE-2025-24803: MobSF Stored Cross-Site Scripting (XSS) Vulnerability 8.1 high 4.3.1 07 Jul 2026
CVE-2026-24490: MobSF Stored XSS Vulnerability via Manifest Analysis 8.1 high 4.4.5 07 Jul 2026
CVE-2025-24803: MobSF Stored Cross-Site Scripting (XSS) Vulnerability 8.1 high 4.3.1 05 Feb 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About mobsf

Is mobsf safe to use?

Vulert records 43 vulnerabilities for mobsf in PyPI: 0 critical, 8 high, 11 medium and 2 low, plus 22 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is mobsf's Vulert package health score?

Vulert scores mobsf 58/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of mobsf affected?

Yes. 4.5.3, the version you would install today, has 3 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of mobsf should I use?

4.5.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does mobsf have?

43 vulnerabilities are recorded for mobsf in the PyPI ecosystem: 0 critical, 8 high, 11 medium and 2 low, plus 22 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mobsf vulnerabilities disclosed?

24 vulnerabilities were recorded for mobsf in the last 12 months, and the oldest entry in this database dates to 18 Oct 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of mobsf are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor mobsf for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mobsf version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.