How severe is CVE-2025-32439?

CVE-2025-32439 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-32439?

CVE-2025-32439 affects the following packages: pleezer (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2025-32439?

Update pleezer to 0.16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32439 is resolved across your whole dependency graph.

How do I detect CVE-2025-32439 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pleezer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-32439 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2025-32439 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-32439 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 CVE-2025-32439?

CVE-2025-32439 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 33th 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.

What type of vulnerability is CVE-2025-32439?

CVE-2025-32439 is classified as CWE-460 (CWE-460). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-32439 published, and has it been updated?

CVE-2025-32439 was published on April 15, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

MEDIUM severity

CVE-2025-32439 — pleezer

MEDIUMFix: roderickvd/pleezer@436a5f1

CVE-2025-32439 is a medium-severity (CVSS 6.5) CWE-460 vulnerability in pleezer. A fix is available for pleezer — see the affected versions and patch details below.

pleezer allows resource exhaustion through uncollected hook script processes

Also known asGHSA-472w-7w45-g3w5

Published

Apr 15, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-32439.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🦀pleezer

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

Impact

Hook scripts in pleezer can be triggered by various events like track changes and playback state changes. In affected versions, these scripts were spawned without proper process cleanup, leaving zombie processes in the system's process table.

Even during normal usage, every track change and playback event would leave behind zombie processes. This leads to inevitable resource exhaustion over time as the system's process table fills up, eventually preventing new processes from being created. The issue is exacerbated if events occur rapidly, whether through normal use (e.g., skipping through a playlist) or potential manipulation of the Deezer Connect protocol traffic.

This vulnerability affects all users who have configured hook scripts using the --hook option.

Patches

This issue has been fixed in version 0.16.0. Users should upgrade to this version, which properly manages child processes using asynchronous process handling and cleanup.

Workarounds

Users who cannot upgrade immediately can:

Disable hook scripts by removing the --hook option
Ensure hook scripts handle their own child process cleanup
Regularly restart pleezer to clear accumulated zombie processes

References

Initial report: https://github.com/roderickvd/pleezer/discussions/83#discussioncomment-12818199
Fix commit: 436a5f1e4c08989b58dbba2b0ffa423458016c2d
Fixed release: https://github.com/roderickvd/pleezer/releases/tag/v0.16.0

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`pleezer`	all versions	0.16.0`cargo update -p pleezer --precise 0.16.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for pleezer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update pleezer to 0.16.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32439 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### Impact Hook scripts in pleezer can be triggered by various events like track changes and playback state changes. In affected versions, these scripts were spawned without proper process cleanup, leaving zombie processes in the system's process table. Even during normal usage, every track change and playback event would leave behind zombie processes. This leads to inevitable resource exhaustion over time as the system's process table fills up, eventually preventing new processes from being created. The issue is exacerbated if events occur rapidly, whether through normal use (e.g., skipping