VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

ms-swift: vulnerability history, versions and safety

ms-swift is a package in the PyPI ecosystem. Vulert records 7 vulnerabilities for it across 120 releases, from Jul 2025 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded M2 L2 U3
i
6 with no fix published

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

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

Most recent disclosure 23 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ms-swift vulnerabilities

Vulert verdict on ms-swift 4.6.0 i

Updated on 23 Oct 2026

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

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

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.6.0 — affected i
  • Vulnerabilities on record 7 over 1 year · 4 in the last year i
  • Latest disclosure 23 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 6 i
  • Depended on by 6 packages i
  • Stars 15,872 i
  • Last release this month i
  • Licence Apache-2.0 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 ms-swift, 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.6.0 13 Oct 2026 M2 L2 U2 Apache-2.0 No Details →
4.5.3 08 Sep 2026 M2 L2 U2 Apache-2.0 No Details →
4.5.2 16 Aug 2026 M2 L2 U2 Apache-2.0 No Details →
4.5.1 16 Aug 2026 M2 L2 U2 Apache-2.0 No Details →
4.5.0 14 Aug 2026 M2 L2 U2 Apache-2.0 No Details →
4.5.0.dev0 03 Aug 2026 M2 L2 U2 Apache-2.0 No Details →
4.4.2 21 Jul 2026 M2 L2 U2 Apache-2.0 No Details →
4.4.1 13 Jul 2026 M2 L2 U2 Apache-2.0 No Details →
4.4.0 06 Jul 2026 M2 L2 U2 Apache-2.0 No Details →
4.3.2 29 Jun 2026 M2 L2 U2 Apache-2.0 No Details →
4.3.1 17 Jun 2026 M2 L2 U2 Apache-2.0 No Details →
4.3.0 10 Jun 2026 M2 L2 U2 Apache-2.0 No Details →
4.2.3 31 May 2026 M2 L2 U2 Apache-2.0 No Details →
4.2.2 24 May 2026 M2 L2 U2 Apache-2.0 No Details →
4.2.1 17 May 2026 M2 L2 U2 Apache-2.0 No Details →
4.2.0 07 May 2026 L1 U1 Apache-2.0 No Details →
4.1.3 25 Apr 2026 L1 U1 Apache-2.0 No Details →
4.1.2 18 Apr 2026 L1 U1 Apache-2.0 No Details →
4.1.1 13 Apr 2026 L1 U1 Apache-2.0 No Details →
4.1.0 07 Apr 2026 L1 U1 Apache-2.0 No Details →
4.0.4 03 Apr 2026 L1 U1 Apache-2.0 No Details →
4.0.3 29 Mar 2026 L1 U1 Apache-2.0 No Details →
4.0.2 14 Mar 2026 L1 U1 Apache-2.0 No Details →
4.0.1 08 Mar 2026 L1 U1 Apache-2.0 No Details →
4.0.0 03 Mar 2026 L1 U1 Apache-2.0 No Details →
3.12.6 28 Feb 2026 L1 U1 Apache-2.0 No Details →
3.12.5 14 Feb 2026 L1 U1 Apache-2.0 No Details →
3.12.4 03 Feb 2026 L1 U1 Apache-2.0 No Details →
3.12.3 24 Jan 2026 L1 U1 Apache-2.0 No Details →
3.12.2 17 Jan 2026 L1 U1 Apache-2.0 No Details →
3.12.1 08 Jan 2026 L1 U1 Apache-2.0 No Details →
3.12.0 30 Dec 2025 L1 U1 Apache-2.0 No Details →
3.11.3 28 Dec 2025 L1 U1 Apache-2.0 No Details →
3.11.2 21 Dec 2025 L1 U1 Apache-2.0 No Details →
3.11.1 15 Dec 2025 L1 U1 Apache-2.0 No Details →
3.11.0 09 Dec 2025 L1 U1 Apache-2.0 No Details →
3.10.3 30 Nov 2025 L1 U1 Apache-2.0 No Details →
3.10.2 23 Nov 2025 L1 U1 Apache-2.0 No Details →
3.10.1 16 Nov 2025 L1 U1 Apache-2.0 No Details →
3.10.0 11 Nov 2025 L1 U1 Apache-2.0 No Details →
3.9.3 04 Nov 2025 L1 U1 Apache-2.0 No Details →
3.9.2 26 Oct 2025 L1 U1 Apache-2.0 No Details →
3.9.1 19 Oct 2025 L1 U1 Apache-2.0 No Details →
3.9.0 13 Oct 2025 L1 U1 Apache-2.0 No Details →
3.8.3 01 Oct 2025 L1 U1 Apache-2.0 No Details →
3.8.2 23 Sep 2025 L1 U1 Apache-2.0 No Details →
3.8.1 15 Sep 2025 L1 U1 Apache-2.0 No Details →
3.8.0 09 Sep 2025 L1 U1 Apache-2.0 No Details →
3.7.3 30 Aug 2025 L1 U1 Apache-2.0 No Details →
3.7.2 21 Aug 2025 L1 U1 Apache-2.0 No Details →
3.7.1 16 Aug 2025 L1 U1 Apache-2.0 No Details →
3.7.0 07 Aug 2025 L1 U1 Apache-2.0 No Details →
3.6.4 02 Aug 2025 L1 U2 Apache-2.0 No Details →
3.6.3 29 Jul 2025 M2 L2 U3 Apache-2.0 No Details →
3.6.2 18 Jul 2025 M2 L2 U3 Apache-2.0 No Details →
3.6.1 11 Jul 2025 M2 L2 U3 Apache-2.0 No Details →
3.6.0 08 Jul 2025 M2 L2 U3 Apache-2.0 No Details →
3.5.3 27 Jun 2025 M2 L2 U3 Apache-2.0 No Details →
3.5.2 20 Jun 2025 M2 L2 U3 Apache-2.0 No Details →
3.5.1 13 Jun 2025 M2 L2 U3 Apache-2.0 No Details →
3.5.0 08 Jun 2025 M2 L2 U3 Apache-2.0 No Details →
3.4.1.post1 18 May 2025 M2 L2 U3 Apache-2.0 No Details →
3.4.1 13 May 2025 M2 L2 U3 Apache-2.0 No Details →
3.4.0 30 Apr 2025 M2 L2 U3 Apache-2.0 No Details →
3.3.1 26 Apr 2025 M2 L2 U3 Apache-2.0 No Details →
3.3.0.post1 12 Apr 2025 M2 L2 U3 Apache-2.0 No Details →
3.3.0 11 Apr 2025 M2 L2 U3 Apache-2.0 No Details →
3.2.2 25 Mar 2025 M2 L2 U3 Apache-2.0 No Details →
3.2.1 14 Mar 2025 M2 L2 U3 Apache-2.0 No Details →
3.2.0.post2 06 Mar 2025 M2 L2 U3 Apache-2.0 No Details →
3.2.0 04 Mar 2025 M2 L2 U3 Apache-2.0 No Details →
3.1.1.post1 24 Feb 2025 M2 L2 U3 Apache-2.0 No Details →
3.1.1 20 Feb 2025 M2 L2 U3 Apache-2.0 No Details →
3.1.0 07 Feb 2025 M2 L2 U3 Apache-2.0 No Details →
3.0.3 22 Jan 2025 M2 L2 U3 Apache-2.0 No Details →
3.0.2.post1 10 Jan 2025 M2 L2 U3 Apache-2.0 No Details →
3.0.2 07 Jan 2025 M2 L2 U3 Apache-2.0 No Details →
3.0.1.post1 29 Dec 2024 M2 L2 U3 Apache-2.0 No Details →
3.0.1 27 Dec 2024 M2 L2 U3 Apache-2.0 No Details →
3.0.0 20 Dec 2024 M2 L2 U3 Apache-2.0 No Details →
2.6.1 29 Nov 2024 M2 L2 U3 Apache-2.0 No Details →
2.6.0.post2 23 Nov 2024 M2 L2 U3 Apache-2.0 No Details →
2.6.0.post1 19 Nov 2024 M2 L2 U3 Apache-2.0 No Details →
2.6.0 13 Nov 2024 M2 L2 U3 Apache-2.0 No Details →
2.5.2.post1 08 Nov 2024 M2 L2 U3 Apache-2.0 No Details →
2.5.2 02 Nov 2024 M2 L2 U3 Apache-2.0 No Details →
2.5.1.post1 26 Oct 2024 M2 L2 U3 Apache-2.0 No Details →
2.5.1 21 Oct 2024 M2 L2 U3 Apache-2.0 No Details →
2.5.0.post1 14 Oct 2024 M2 L2 U3 Apache-2.0 No Details →
2.4.2.post2 24 Sep 2024 M2 L2 U3 Apache-2.0 No Details →
2.4.2.post1 23 Sep 2024 M2 L2 U3 Apache-2.0 No Details →
2.4.2 18 Sep 2024 M2 L2 U3 Apache-2.0 No Details →
2.4.1 09 Sep 2024 M2 L2 U3 Apache-2.0 No Details →
2.4.0.post1 02 Sep 2024 M2 L2 U3 Apache-2.0 No Details →
2.4.0 02 Sep 2024 M2 L2 U3 Apache-2.0 No Details →
2.3.2.post1 28 Aug 2024 M2 L2 U3 Apache-2.0 No Details →
2.3.2 24 Aug 2024 M2 L2 U3 Apache-2.0 No Details →
2.3.1 19 Aug 2024 M2 L2 U3 Apache-2.0 No Details →
2.3.0.post1 11 Aug 2024 M2 L2 U3 Apache-2.0 No Details →
2.3.0 09 Aug 2024 M2 L2 U3 Apache-2.0 No Details →
2.2.5 02 Aug 2024 M2 L2 U3 — No Details →
2.2.4 26 Jul 2024 M2 L2 U3 — No Details →
2.2.3 20 Jul 2024 M2 L2 U3 — No Details →
2.2.2 13 Jul 2024 M2 L2 U3 — No Details →
2.2.1 08 Jul 2024 M2 L2 U3 — No Details →
2.2.0 05 Jul 2024 M2 L2 U3 — No Details →
2.1.1.post2 18 Jun 2024 M2 L2 U3 — No Details →
2.1.1.post1 17 Jun 2024 M2 L2 U3 — No Details →
2.1.1 17 Jun 2024 M2 L2 U3 — No Details →
2.1.0 07 Jun 2024 M2 L2 U3 — No Details →
2.0.5.post1 28 May 2024 M2 L2 U3 — No Details →
2.0.5 22 May 2024 M2 L2 U3 — No Details →
2.0.4 01 May 2024 M2 L2 U3 — No Details →
2.0.3.post1 24 Apr 2024 M2 L2 U3 — No Details →
2.0.3 23 Apr 2024 M2 L2 U3 — No Details →
2.0.2 17 Apr 2024 M2 L2 U3 — No Details →
2.0.1 17 Apr 2024 M2 L2 U3 — No Details →
2.0.0 15 Apr 2024 M2 L2 U3 — No Details →
1.7.3 17 Mar 2024 M2 L2 U3 — No Details →
1.7.2 11 Mar 2024 M2 L2 U3 — No Details →

The newest 120 of 137 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 3
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for ms-swift

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-50460: MS SWIFT Remote Code Execution via Unsafe PyYAML Deserialization 9.8 low No fix published 31 Jul 2025
CVE-2025-50460: ms-swift Remote Code Execution via Unsafe PyYAML Deserialization 9.8 critical No fix published 07 Jul 2026
Remote Code Execution Vulnerability in MS SWIFT Package 6.6 medium No fix published 31 Jul 2025
Remote Code Execution Vulnerability in MS SWIFT Package 5.1 medium No fix published 31 Jul 2025
CVE-2025-41419: ms-swift RCE Vulnerability in Web-UI 5.1 medium 3.7.0 07 Jul 2026

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

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 ms-swift

Is ms-swift safe to use?

Vulert records 7 vulnerabilities for ms-swift in PyPI: 0 critical, 0 high, 2 medium and 2 low, plus 3 not yet rated. 6 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is ms-swift's Vulert package health score?

Vulert scores ms-swift 50/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 ms-swift affected?

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

Which version of ms-swift should I use?

4.6.0 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 ms-swift have?

7 vulnerabilities are recorded for ms-swift in the PyPI ecosystem: 0 critical, 0 high, 2 medium and 2 low, plus 3 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 ms-swift vulnerabilities disclosed?

4 vulnerabilities were recorded for ms-swift in the last 12 months, and the oldest entry in this database dates to 31 Jul 2025. 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 ms-swift 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 ms-swift for upcoming vulnerabilities?

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