https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 20 Oct 2026 03:28:11 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-261561 EUVD-2026-261561 https://cve.radiocsirt.org/vuln/euvd-2026-261561 https://cve.radiocsirt.org/vuln/fkie_cve-2024-9979 <p>A flaw was found in PyO3. This vulnerability causes a use-after-free issue, potentially leading to memory corruption or crashes via unsound borrowing from weak Python references.</p> <p>A flaw was found in PyO3. This vulnerability causes a use-after-free issue, potentially leading to memory corruption or crashes via unsound borrowing from weak Python references.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2024-9979 https://cve.radiocsirt.org/vuln/ghsa-6jgw-rgmm-7cv6 <p><strong>Affected:</strong> crates.io: pyo3</p> <p>The family of functions to read &#34;borrowed&#34; values from Python weak references were fundamentally unsound, because the weak reference does itself not have ownership of the value. At any point the last strong reference could be cleared and the borrowed value would become dangling.</p> <p>In PyO3 0.22.4 these functions have all been deprecated and patched to leak a strong reference as a mitigation. PyO3 0.23 will remove these functions entirely.</p> <p><strong>Affected:</strong> crates.io: pyo3</p> <p>The family of functions to read &#34;borrowed&#34; values from Python weak references were fundamentally unsound, because the weak reference does itself not have ownership of the value. At any point the last strong reference could be cleared and the borrowed value would become dangling.</p> <p>In PyO3 0.22.4 these functions have all been deprecated and patched to leak a strong reference as a mitigation. PyO3 0.23 will remove these functions entirely.</p> https://cve.radiocsirt.org/vuln/ghsa-6jgw-rgmm-7cv6 https://cve.radiocsirt.org/vuln/rustsec-2024-0378 <p><strong>Affected:</strong> crates.io: pyo3</p> <p>The family of functions to read &#34;borrowed&#34; values from Python weak references were fundamentally unsound, because the weak reference does itself not have ownership of the value. At any point the last strong reference could be cleared and the borrowed value would become dangling.</p> <p>In PyO3 0.22.4 these functions have all been deprecated and patched to leak a strong reference as a mitigation. PyO3 0.23 will remove these functions entirely.</p> <p><strong>Affected:</strong> crates.io: pyo3</p> <p>The family of functions to read &#34;borrowed&#34; values from Python weak references were fundamentally unsound, because the weak reference does itself not have ownership of the value. At any point the last strong reference could be cleared and the borrowed value would become dangling.</p> <p>In PyO3 0.22.4 these functions have all been deprecated and patched to leak a strong reference as a mitigation. PyO3 0.23 will remove these functions entirely.</p> https://cve.radiocsirt.org/vuln/rustsec-2024-0378 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-9979 <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> Ubuntu:24.04:LTS: rust-pyo3</p> <p>A flaw was found in PyO3. This vulnerability causes a use-after-free issue, potentially leading to memory corruption or crashes via unsound borrowing from weak Python references.</p> <p><strong>Withdrawn by the publisher.</strong></p> <p><strong>Affected:</strong> Ubuntu:24.04:LTS: rust-pyo3</p> <p>A flaw was found in PyO3. This vulnerability causes a use-after-free issue, potentially leading to memory corruption or crashes via unsound borrowing from weak Python references.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-9979