MS SWIFT Deserialization RCE Vulnerability
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI ms-swift
- Affected
- <= 3.6.3
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-r54c-2xmf-2cf3 lists affected ranges: PyPI ms-swift >=0 <=3.6.3
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-r54c-2xmf-2cf3 lists affected ranges: PyPI ms-swift >=0 <=3.6.3
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 6.6 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P · score source
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
This appears to be a security vulnerability report describing a remote code execution (RCE) exploit in the ms-swift framework through malicious pickle deserialization in adapter model files. The vulnerability allows arbitrary command execution when loading specially crafted adapter models from ModelScope. This occurs when using machine torch version < 2.6.0, while ms-swift accepts torch version = 2.0 I. Detailed Description: 1. Install ms-swift 2. Start web-ui 3. After startup, you can access http://localhost:7860/ through your browser to see the launched fine-tuning framework program 4. Upload an adapter model repository (cyjhhh/loraadapter4llama3) on ModelScope, where the lora/adaptermodel.bin file is generated through the following code: 5. First training submission: First, fill in the required parameters in the LLM Training interface, including Model id and Dataset Code, and configure the following in the Other params section of Advanced settings 6. Click Begin to submit. You can…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-r54c-2xmf-2cf3
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-r54c-2xmf-2cf3
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-r54c-2xmf-2cf3 Advisory: MS SWIFT Deserialization RCE Vulnerability IDs: GHSA-r54c-2xmf-2cf3 Record: https://patchnext.com/advisories/ghsa-r54c-2xmf-2cf3 (revision 3, 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 6.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - PyPI ms-swift: affected <= 3.6.3 ## Suggested inspection (read-only) - `python -m pip show ms-swift`: prints the installed version. Run with the environment that serves production active. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on ms-swift. - 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-r54c-2xmf-2cf3 (OSV record GHSA-r54c-2xmf-2cf3 lists affected ranges: PyPI ms-swift >=0 <=3.6.3) - Verified: https://github.com/advisories/GHSA-r54c-2xmf-2cf3 (GitHub-reviewed advisory GHSA-r54c-2xmf-2cf3 lists affected ranges: PyPI ms-swift >=0 <=3.6.3) Commands are suggestions: review each one before running it.
Loading voting…