<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 19 Oct 2026 17:14:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-50460</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-50460</link>
      <description>&lt;p&gt;A remote code execution (RCE) vulnerability exists in the ms-swift project version 3.3.0 due to unsafe deserialization in tests/run.py using yaml.load() from the PyYAML library (versions = 5.3.1). If an attacker can control the content of the YAML configuration file passed to the --run_config parameter, arbitrary code can be executed during deserialization. This can lead to full system compromise. The vulnerability is triggered when a malicious YAML file is loaded, allowing the execution of arbitrary Python commands such as os.system(). It is recommended to upgrade PyYAML to version 5.4 or higher, and to use yaml.safe_load() to mitigate the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A remote code execution (RCE) vulnerability exists in the ms-swift project version 3.3.0 due to unsafe deserialization in tests/run.py using yaml.load() from the PyYAML library (versions = 5.3.1). If an attacker can control the content of the YAML configuration file passed to the --run_config parameter, arbitrary code can be executed during deserialization. This can lead to full system compromise. The vulnerability is triggered when a malicious YAML file is loaded, allowing the execution of arbitrary Python commands such as os.system(). It is recommended to upgrade PyYAML to version 5.4 or higher, and to use yaml.safe_load() to mitigate the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-50460</guid>
    </item>
    <item>
      <title>PYSEC-2026-1683 — MS SWIFT Remote Code Execution via unsafe PyYAML deserialization</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-1683</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ms-swift&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;A Remote Code Execution (RCE) vulnerability exists in the [modelscope/ms-swift](https://github.com/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`.&lt;/p&gt;
&lt;p&gt;If an attacker can control or replace the YAML configuration file provided to the `--run_config` argument, they may inject a malicious payload that results in arbitrary code execution.&lt;/p&gt;
&lt;p&gt;## Affected Repository&lt;/p&gt;
&lt;p&gt;- **Project:** [modelscope/ms-swift](https://github.com/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 &amp;lt;= 5.3.1&lt;/p&gt;
&lt;p&gt;## Vulnerable Code&lt;/p&gt;
&lt;p&gt;```python
if args.run_config is not None and Path(args.run_config).exists():
    with open(args.run_config, encoding=&amp;#39;utf-8&amp;#39;) as f:
        run_config = yaml.load(f, Loader=yaml.FullLoader)
```&lt;/p&gt;
&lt;p&gt;## Proof of Concept (PoC)&lt;/p&gt;
&lt;p&gt;### Step 1: Create malicious YAML file (`exploit.yaml`)&lt;/p&gt;
&lt;p&gt;```yaml
!!python/object/new:type
args: [&amp;#34;z&amp;#34;, !!python/tuple [], {&amp;#34;extend&amp;#34;: !!python/name:exec }]
listitems: &amp;#34;__import__(&amp;#39;os&amp;#39;).system(&amp;#39;mkdir HACKED&amp;#39;)&amp;#34;
```&lt;/p&gt;
&lt;p&gt;### Step 2: Execute with vulnerable PyYAML (&amp;lt;= 5.3.1)&lt;/p&gt;
&lt;p&gt;```python
import yaml&lt;/p&gt;
&lt;p&gt;with open(&amp;#34;exploit.yaml&amp;#34;, &amp;#34;r&amp;#34;) as f:
    cfg = yaml.lo…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: ms-swift&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;A Remote Code Execution (RCE) vulnerability exists in the [modelscope/ms-swift](https://github.com/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`.&lt;/p&gt;
&lt;p&gt;If an attacker can control or replace the YAML configuration file provided to the `--run_config` argument, they may inject a malicious payload that results in arbitrary code execution.&lt;/p&gt;
&lt;p&gt;## Affected Repository&lt;/p&gt;
&lt;p&gt;- **Project:** [modelscope/ms-swift](https://github.com/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 &amp;lt;= 5.3.1&lt;/p&gt;
&lt;p&gt;## Vulnerable Code&lt;/p&gt;
&lt;p&gt;```python
if args.run_config is not None and Path(args.run_config).exists():
    with open(args.run_config, encoding=&amp;#39;utf-8&amp;#39;) as f:
        run_config = yaml.load(f, Loader=yaml.FullLoader)
```&lt;/p&gt;
&lt;p&gt;## Proof of Concept (PoC)&lt;/p&gt;
&lt;p&gt;### Step 1: Create malicious YAML file (`exploit.yaml`)&lt;/p&gt;
&lt;p&gt;```yaml
!!python/object/new:type
args: [&amp;#34;z&amp;#34;, !!python/tuple [], {&amp;#34;extend&amp;#34;: !!python/name:exec }]
listitems: &amp;#34;__import__(&amp;#39;os&amp;#39;).system(&amp;#39;mkdir HACKED&amp;#39;)&amp;#34;
```&lt;/p&gt;
&lt;p&gt;### Step 2: Execute with vulnerable PyYAML (&amp;lt;= 5.3.1)&lt;/p&gt;
&lt;p&gt;```python
import yaml&lt;/p&gt;
&lt;p&gt;with open(&amp;#34;exploit.yaml&amp;#34;, &amp;#34;r&amp;#34;) as f:
    cfg = yaml.lo…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-1683</guid>
    </item>
  </channel>
</rss>
