How severe is GHSA-wcxc-jf6c-8rx9?

No CVSS score has been assigned to GHSA-wcxc-jf6c-8rx9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wcxc-jf6c-8rx9?

GHSA-wcxc-jf6c-8rx9 affects the following packages: libpulse-binding (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-wcxc-jf6c-8rx9?

Update libpulse-binding to 2.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wcxc-jf6c-8rx9 is resolved across your whole dependency graph.

How do I detect GHSA-wcxc-jf6c-8rx9 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libpulse-binding. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-wcxc-jf6c-8rx9 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-wcxc-jf6c-8rx9?

O3 pinpoints whether GHSA-wcxc-jf6c-8rx9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wcxc-jf6c-8rx9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-wcxc-jf6c-8rx9 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-wcxc-jf6c-8rx9 published, and has it been updated?

GHSA-wcxc-jf6c-8rx9 was published on August 25, 2021 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Withdrawn — this advisory has been retracted

🦀 crates.io

GHSA-wcxc-jf6c-8rx9

GHSA-wcxc-jf6c-8rx9 is a security vulnerability in libpulse-binding. O3 Security confirms whether GHSA-wcxc-jf6c-8rx9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Duplicate Advisory: Uncaught Exception in libpulse-binding

Also known asCVE-2019-25055 GHSA-xvcg-2q82-r87jRUSTSEC-2019-0038

Published

Aug 25, 2021

Updated

Feb 3, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🦀libpulse-binding

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-xvcg-2q82-r87j. This link is maintained to preserve external references.

Original Description

Affected versions of this crate failed to catch panics crossing FFI boundaries via callbacks, which is a form of UB. This flaw was corrected by [this commit][1] which was included in version 2.6.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`libpulse-binding`	all versions	2.6.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libpulse-binding. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update libpulse-binding to 2.6.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wcxc-jf6c-8rx9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-wcxc-jf6c-8rx9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wcxc-jf6c-8rx9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Duplicate Advisory This advisory has been withdrawn because it is a duplicate of GHSA-xvcg-2q82-r87j. This link is maintained to preserve external references. ## Original Description Affected versions of this crate failed to catch panics crossing FFI boundaries via callbacks, which is a form of UB. This flaw was corrected by [this commit][1] which was included in version 2.6.0.

O3 Security · Impact-Aware SCA

Is GHSA-wcxc-jf6c-8rx9 in your dependencies?

O3 detects GHSA-wcxc-jf6c-8rx9 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works