Rust advisories / crate
Security history · libpulse-binding · data from Oct 24, 2026
Is libpulse-binding safe to use? Its security history
VerdictNo open advisories. 2 past vulnerabilities were fixed; use 2.6.0 or newer to be clear of all of them.
3advisories on record
2vulnerabilities
0unmaintained notices
2.6.0newest fixed version
Every advisory, newest first
- UnsoundRUSTSEC-2019-0038 · 2019-03-10Fix for UB in failure to catch panics crossing FFI boundaries
- Vulnerability MediumRUSTSEC-2018-0020 · 2018-12-22Possible use-after-free with `proplist::Iterator`
- VulnerabilityRUSTSEC-2018-0021 · 2018-06-15Use-after-free with objects returned by `Stream`'s `get_format_info` and `get_context` methods
Check your version
Run cargo tree -i libpulse-binding 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.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Are you affected?Check your whole dependency treeRead it next →Also worth your time
Did this answer your question?