Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.3amended

MS SWIFT Remote Code Execution via unsafe PyYAML deserialization

CVE-2025-50460GHSA-fm6c-f59h-7mmg

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.

Add to your agent

Affected packages

  • PyPI ms-swift

    Affected
    <= 3.6.3
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2025-50460: 2.88% estimated exploitation activity in the next 30 days; percentile 86.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Description A Remote Code Execution (RCE) vulnerability exists in the modelscope/ms-swift project due to unsafe use of yaml.load() in combination with vulnerable versions of the PyYAML library (≤ 5.3.1). The issue resides in the tests/run.py script, where a user-supplied YAML configuration file is deserialized using yaml.load() with yaml.FullLoader. If an attacker can control or replace the YAML configuration file provided to the --runconfig argument, they may inject a malicious payload that results in arbitrary code execution. Affected Repository - Project: modelscope/ms-swift - Affect versions: latest - File: tests/run.py - GitHub Permalink: https://github.com/modelscope/ms-swift/blob/e02ebfdf34f979bbdba9d935acc1689f8d227b38/tests/run.py#L420 - Dependency: PyYAML <= 5.3.1 Vulnerable Code Proof of Concept (PoC) Step 1: Create malicious YAML file (exploit.yaml) Step 2: Execute with vulnerable PyYAML (<= 5.3.1) This results in execution of os.system, proving code execution. Mitigation…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-fm6c-f59h-7mmg

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-fm6c-f59h-7mmg

Agent brief

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

# Patch Next advisory brief: CVE-2025-50460

Advisory: MS SWIFT Remote Code Execution via unsafe PyYAML deserialization
IDs: CVE-2025-50460, GHSA-fm6c-f59h-7mmg
Record: https://patchnext.com/advisories/cve-2025-50460 (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: Low (CVSS 2.3)
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-fm6c-f59h-7mmg (OSV record GHSA-fm6c-f59h-7mmg lists affected ranges: PyPI ms-swift >=0 <=3.6.3)
- Verified: https://github.com/advisories/GHSA-fm6c-f59h-7mmg (GitHub-reviewed advisory GHSA-fm6c-f59h-7mmg lists affected ranges: PyPI ms-swift >=0 <=3.6.3)

Commands are suggestions: review each one before running it.

Loading voting…