CVE-2025-32439

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

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.

CVE-2025-32439 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.16.0); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2025-32439? CVE-2025-32439 is a medium-severity security vulnerability in pleezer (rust), affecting versions < 0.16.0. It is fixed in 0.16.0.
2. How severe is CVE-2025-32439? CVE-2025-32439 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of pleezer are affected by CVE-2025-32439? pleezer (rust) versions < 0.16.0 is affected.
4. Is there a fix for CVE-2025-32439? Yes. CVE-2025-32439 is fixed in 0.16.0. Upgrade to this version or later.
5. Is CVE-2025-32439 exploitable, and should I be worried? Whether CVE-2025-32439 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-32439 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-32439? Upgrade pleezer to 0.16.0 or later.