<?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>Wed, 07 Oct 2026 22:14:30 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-15288</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-15288</link>
      <description>bdu:2025-15288</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-15288</guid>
    </item>
    <item>
      <title>EUVD-2026-252852</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-252852</link>
      <description>EUVD-2026-252852</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-252852</guid>
    </item>
    <item>
      <title>fkie_cve-2025-10157</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-10157</link>
      <description>&lt;p&gt;A Protection Mechanism Failure vulnerability in mmaitre314 picklescan versions up to and including 0.0.30 allows a remote attacker to bypass the unsafe globals check. This is possible because the scanner performs an exact match for module names, allowing malicious payloads to be loaded via submodules of dangerous packages (e.g., &amp;#39;asyncio.unix_events&amp;#39; instead of &amp;#39;asyncio&amp;#39;).&lt;/p&gt;
&lt;p&gt;When the incorrectly considered safe file is loaded after scan, it can lead to the execution of malicious code.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A Protection Mechanism Failure vulnerability in mmaitre314 picklescan versions up to and including 0.0.30 allows a remote attacker to bypass the unsafe globals check. This is possible because the scanner performs an exact match for module names, allowing malicious payloads to be loaded via submodules of dangerous packages (e.g., &amp;#39;asyncio.unix_events&amp;#39; instead of &amp;#39;asyncio&amp;#39;).&lt;/p&gt;
&lt;p&gt;When the incorrectly considered safe file is loaded after scan, it can lead to the execution of malicious code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-10157</guid>
    </item>
    <item>
      <title>GHSA-f7qq-56ww-84cr — Picklescan is Vulnerable to Unsafe Globals Check Bypass through Subclass Imports</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f7qq-56ww-84cr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: picklescan&lt;/p&gt;
&lt;p&gt;### Summary
The vulnerability allows malicious actors to bypass PickleScan&amp;#39;s unsafe globals check, leading to potential arbitrary code execution. The issue stems from PickleScan&amp;#39;s strict check for full module names against its list of unsafe globals. By using subclasses of dangerous imports instead of the exact module names, attackers can circumvent the check and inject malicious payloads.&lt;/p&gt;
&lt;p&gt;### PoC
1. Download a model that uses the `asyncio` package:&lt;/p&gt;
&lt;p&gt;```wget https://huggingface.co/iluem/linux_pkl/resolve/main/asyncio_asyncio_unix_events___UnixSubprocessTransport__start.pkl```&lt;/p&gt;
&lt;p&gt;2. Check with PickleScan: `picklescan -p asyncio_asyncio_unix_events___UnixSubprocessTransport__start.pkl -g`&lt;/p&gt;
&lt;p&gt;**Expected Result:**&lt;/p&gt;
&lt;p&gt;PickleScan should identify all `asyncio` import as dangerous and flag the pickle file as malicious as `asyncio` is in `_unsafe_globals` dictionary.&lt;/p&gt;
&lt;p&gt;**Actual Result:**
![Screenshot 2025-06-29 at 14 13 38](https://github.com/user-attachments/assets/39467f50-5cdb-4c25-bb37-35c03dc4a626)&lt;/p&gt;
&lt;p&gt;PickleScan marked the import as Suspicious, failing to identify it as a dangerous import.&lt;/p&gt;
&lt;p&gt;### Impact
**Severity**: High
**Affected Users**: Any organization, like HuggingFace, or individual using PickleScan to analyze PyTorch models or other files distributed as ZIP archives for malicious pickle content.
**Impact Details**: Attackers can craft malicious PyTorch models containing embedded pickle payloads, package them into ZIP archives, and bypass the PickleScan check by using subclasses…&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
The vulnerability allows malicious actors to bypass PickleScan&amp;#39;s unsafe globals check, leading to potential arbitrary code execution. The issue stems from PickleScan&amp;#39;s strict check for full module names against its list of unsafe globals. By using subclasses of dangerous imports instead of the exact module names, attackers can circumvent the check and inject malicious payloads.&lt;/p&gt;
&lt;p&gt;### PoC
1. Download a model that uses the `asyncio` package:&lt;/p&gt;
&lt;p&gt;```wget https://huggingface.co/iluem/linux_pkl/resolve/main/asyncio_asyncio_unix_events___UnixSubprocessTransport__start.pkl```&lt;/p&gt;
&lt;p&gt;2. Check with PickleScan: `picklescan -p asyncio_asyncio_unix_events___UnixSubprocessTransport__start.pkl -g`&lt;/p&gt;
&lt;p&gt;**Expected Result:**&lt;/p&gt;
&lt;p&gt;PickleScan should identify all `asyncio` import as dangerous and flag the pickle file as malicious as `asyncio` is in `_unsafe_globals` dictionary.&lt;/p&gt;
&lt;p&gt;**Actual Result:**
![Screenshot 2025-06-29 at 14 13 38](https://github.com/user-attachments/assets/39467f50-5cdb-4c25-bb37-35c03dc4a626)&lt;/p&gt;
&lt;p&gt;PickleScan marked the import as Suspicious, failing to identify it as a dangerous import.&lt;/p&gt;
&lt;p&gt;### Impact
**Severity**: High
**Affected Users**: Any organization, like HuggingFace, or individual using PickleScan to analyze PyTorch models or other files distributed as ZIP archives for malicious pickle content.
**Impact Details**: Attackers can craft malicious PyTorch models containing embedded pickle payloads, package them into ZIP archives, and bypass the PickleScan check by using subclasses…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f7qq-56ww-84cr</guid>
    </item>
    <item>
      <title>PYSEC-2025-153</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2025-153</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: picklescan&lt;/p&gt;
&lt;p&gt;A Protection Mechanism Failure vulnerability in mmaitre314 picklescan versions up to and including 0.0.30 allows a remote attacker to bypass the unsafe globals check. This is possible because the scanner performs an exact match for module names, allowing malicious payloads to be loaded via submodules of dangerous packages (e.g., &amp;#39;asyncio.unix_events&amp;#39; instead of &amp;#39;asyncio&amp;#39;).&lt;/p&gt;
&lt;p&gt;When the incorrectly considered safe file is loaded after scan, it can lead to the execution of malicious code.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: picklescan&lt;/p&gt;
&lt;p&gt;A Protection Mechanism Failure vulnerability in mmaitre314 picklescan versions up to and including 0.0.30 allows a remote attacker to bypass the unsafe globals check. This is possible because the scanner performs an exact match for module names, allowing malicious payloads to be loaded via submodules of dangerous packages (e.g., &amp;#39;asyncio.unix_events&amp;#39; instead of &amp;#39;asyncio&amp;#39;).&lt;/p&gt;
&lt;p&gt;When the incorrectly considered safe file is loaded after scan, it can lead to the execution of malicious code.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2025-153</guid>
    </item>
  </channel>
</rss>
