Rust advisories / crate
Security history · pyo3 · data from Oct 24, 2026
Is pyo3 safe to use? Its security history
VerdictNo open advisories. 7 past vulnerabilities were fixed; use 0.29.0 or newer to be clear of all of them.
7advisories on record
7vulnerabilities
0unmaintained notices
0.29.0newest fixed version
Every advisory, newest first
- VulnerabilityRUSTSEC-2026-0176 · 2026-06-11Out-of-bounds read in `nth` / `nth_back` for `PyList` and `PyTuple` iterators
- VulnerabilityRUSTSEC-2026-0177 · 2026-06-11Missing `Sync` bound on `PyCFunction::new_closure` closures
- VulnerabilityRUSTSEC-2026-0013 · 2026-02-18Type confusion when accessing data from sublasses of subclasses of native types with `abi3` feature targeting Python 3.12 and up
- VulnerabilityRUSTSEC-2025-0020 · 2025-04-01Risk of buffer overflow in `PyString::from_object`
- VulnerabilityRUSTSEC-2024-0409 · 2024-12-04Build corruption when using `PYO3_CONFIG_FILE` environment variable
- VulnerabilityRUSTSEC-2024-0378 · 2024-10-12Risk of use-after-free in `borrowed` reads from Python weak references
- Vulnerability MediumRUSTSEC-2020-0074 · 2020-11-28Reference counting error in `From<Py<T>>`
Check your version
Run cargo tree -i pyo3 to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
Download trends, dependents and alternatives: pyo3 crate data.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Before you depend on itpyo3 crate dataReal downloads, dependents and alternatives.Read it next →Did this answer your question?