https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-15T08:50:23.082048+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-241630 EUVD-2026-241630 2026-10-15T08:50:23.084570+00:00 EUVD-2026-241630 https://cve.radiocsirt.org/vuln/fkie_cve-2025-5174 fkie_cve-2025-5174 2026-10-15T08:50:23.084600+00:00

A vulnerability was found in erdogant pypickle up to 1.1.5 and classified as problematic. Affected by this issue is the function load of the file pypickle/pypickle.py. The manipulation leads to deserialization. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The patch is identified as 14b4cae704a0bb4eb6723e238f25382d847a1917. It is recommended to upgrade the affected component.

 https://cve.radiocsirt.org/vuln/ghsa-5qwj-342r-h886 GHSA-5qwj-342r-h886 — pypickle unsafe deserialization vulnerability 2026-10-15T08:50:23.084631+00:00

Affected: PyPI: pypickle

A vulnerability was found in erdogant pypickle up to 1.1.5 and classified as problematic. Affected by this issue is the function load of the file pypickle/pypickle.py. The manipulation leads to deserialization. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The patch is identified as 14b4cae704a0bb4eb6723e238f25382d847a1917. It is recommended to upgrade the affected component.

 https://cve.radiocsirt.org/vuln/pysec-2025-45 PYSEC-2025-45 2026-10-15T08:50:23.084655+00:00

Affected: PyPI: pypickle

A vulnerability was found in erdogant pypickle up to 1.1.5 and classified as problematic. Affected by this issue is the function load of the file pypickle/pypickle.py. The manipulation leads to deserialization. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. Upgrading to version 2.0.0 is able to address this issue. The patch is identified as 14b4cae704a0bb4eb6723e238f25382d847a1917. It is recommended to upgrade the affected component.