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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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.

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.

What is the EPSS score for GHSA-wcxc-jf6c-8rx9?

GHSA-wcxc-jf6c-8rx9 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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

Not in CISA KEV

Duplicate Advisory: Uncaught Exception in libpulse-bindingGHSA-wcxc-jf6c-8rx9

Fix: jnqnfe/pulse-binding-rust@7fd282a

GHSA-wcxc-jf6c-8rx9 is a security vulnerability in libpulse-binding. A fix is available for libpulse-binding — see the affected versions and patch details below.

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

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

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`cargo update -p libpulse-binding --precise 2.6.0`

Affected Products

1 product · 1 configurations

Application

libpulse-bindinglibpulse-binding_project

< 2.6.0

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.

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?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works