https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 13:32:25 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-15286 bdu:2025-15286 https://cve.radiocsirt.org/vuln/bdu:2025-15286 https://cve.radiocsirt.org/vuln/euvd-2026-252849 EUVD-2026-252849 https://cve.radiocsirt.org/vuln/euvd-2026-252849 https://cve.radiocsirt.org/vuln/fkie_cve-2025-10156 <p>An Improper Handling of Exceptional Conditions vulnerability in the ZIP archive scanning component of mmaitre314 picklescan allows a remote attacker to bypass security scans. This is achieved by crafting a ZIP archive containing a file with a bad Cyclic Redundancy Check (CRC), which causes the scanner to halt and fail to analyze the contents for malicious pickle files. When the file incorrectly considered safe is loaded, it can lead to the execution of malicious code.</p> <p>An Improper Handling of Exceptional Conditions vulnerability in the ZIP archive scanning component of mmaitre314 picklescan allows a remote attacker to bypass security scans. This is achieved by crafting a ZIP archive containing a file with a bad Cyclic Redundancy Check (CRC), which causes the scanner to halt and fail to analyze the contents for malicious pickle files. When the file incorrectly considered safe is loaded, it can lead to the execution of malicious code.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-10156 https://cve.radiocsirt.org/vuln/ghsa-mjqp-26hc-grxg <p><strong>Affected:</strong> PyPI: picklescan</p> <p>### Summary Picklescan&#39;s ability to scan ZIP archives for malicious pickle files is compromised when the archive contains a file with a bad Cyclic Redundancy Check (CRC). Instead of attempting to scan the files within the archive, whatever the CRC is, Picklescan fails in error and returns no results. This allows attackers to potentially hide malicious pickle payloads within ZIP archives that PyTorch might still be able to load (as PyTorch often disables CRC checks).</p> <p>### Details Picklescan likely utilizes Python&#39;s built-in zipfile module to handle ZIP archives. When zipfile encounters a file within an archive that has a mismatch between the declared CRC and the calculated CRC, it can raise an exception (e.g., BadZipFile or a related error). It appears that Picklescan does not try to scan the files whatever the CRC is. This behavior contrasts with PyTorch&#39;s model loading capabilities, which in many cases might bypass CRC checks for ZIP archives - whatever the configuration is. This discrepancy creates a blind spot where a malicious model packaged in a ZIP with a bad CRC could be loaded by PyTorch while being completely missed by Picklescan.</p> <p>### PoC</p> <p>1. Download an existing Pytorch model with a bad CRC</p> <p>`wget &lt;https://huggingface.co/jinaai/jina-embeddings-v2-base-en/resolve/main/pytorch_model.bin?download=true&gt; -O pytorch_model.bin`</p> <p>2. Attempt to scan the corrupted ZIP file with PickleScan:</p> <p>``` # Assuming you have Picklescan installed and in your PATH picklescan -p pytorc…</p> <p><strong>Affected:</strong> PyPI: picklescan</p> <p>### Summary Picklescan&#39;s ability to scan ZIP archives for malicious pickle files is compromised when the archive contains a file with a bad Cyclic Redundancy Check (CRC). Instead of attempting to scan the files within the archive, whatever the CRC is, Picklescan fails in error and returns no results. This allows attackers to potentially hide malicious pickle payloads within ZIP archives that PyTorch might still be able to load (as PyTorch often disables CRC checks).</p> <p>### Details Picklescan likely utilizes Python&#39;s built-in zipfile module to handle ZIP archives. When zipfile encounters a file within an archive that has a mismatch between the declared CRC and the calculated CRC, it can raise an exception (e.g., BadZipFile or a related error). It appears that Picklescan does not try to scan the files whatever the CRC is. This behavior contrasts with PyTorch&#39;s model loading capabilities, which in many cases might bypass CRC checks for ZIP archives - whatever the configuration is. This discrepancy creates a blind spot where a malicious model packaged in a ZIP with a bad CRC could be loaded by PyTorch while being completely missed by Picklescan.</p> <p>### PoC</p> <p>1. Download an existing Pytorch model with a bad CRC</p> <p>`wget &lt;https://huggingface.co/jinaai/jina-embeddings-v2-base-en/resolve/main/pytorch_model.bin?download=true&gt; -O pytorch_model.bin`</p> <p>2. Attempt to scan the corrupted ZIP file with PickleScan:</p> <p>``` # Assuming you have Picklescan installed and in your PATH picklescan -p pytorc…</p> https://cve.radiocsirt.org/vuln/ghsa-mjqp-26hc-grxg https://cve.radiocsirt.org/vuln/pysec-2025-152 <p><strong>Affected:</strong> PyPI: picklescan</p> <p>An Improper Handling of Exceptional Conditions vulnerability in the ZIP archive scanning component of mmaitre314 picklescan allows a remote attacker to bypass security scans. This is achieved by crafting a ZIP archive containing a file with a bad Cyclic Redundancy Check (CRC), which causes the scanner to halt and fail to analyze the contents for malicious pickle files. When the file incorrectly considered safe is loaded, it can lead to the execution of malicious code.</p> <p><strong>Affected:</strong> PyPI: picklescan</p> <p>An Improper Handling of Exceptional Conditions vulnerability in the ZIP archive scanning component of mmaitre314 picklescan allows a remote attacker to bypass security scans. This is achieved by crafting a ZIP archive containing a file with a bad Cyclic Redundancy Check (CRC), which causes the scanner to halt and fail to analyze the contents for malicious pickle files. When the file incorrectly considered safe is loaded, it can lead to the execution of malicious code.</p> https://cve.radiocsirt.org/vuln/pysec-2025-152