<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 07 Oct 2026 01:43:46 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-230562</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-230562</link>
      <description>EUVD-2026-230562</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-230562</guid>
    </item>
    <item>
      <title>fkie_cve-2025-32439</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-32439</link>
      <description>&lt;p&gt;pleezer is a headless Deezer Connect player. Hook scripts in pleezer can be triggered by various events like track changes and playback state changes. In versions before 0.16.0, these scripts were spawned without proper process cleanup, leaving zombie processes in the system&amp;#39;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&amp;#39;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 issue has been fixed in version 0.16.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;pleezer is a headless Deezer Connect player. Hook scripts in pleezer can be triggered by various events like track changes and playback state changes. In versions before 0.16.0, these scripts were spawned without proper process cleanup, leaving zombie processes in the system&amp;#39;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&amp;#39;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 issue has been fixed in version 0.16.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-32439</guid>
    </item>
    <item>
      <title>GHSA-472w-7w45-g3w5 — Pleezer resource exhaustion through uncollected hook script processes</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-472w-7w45-g3w5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: pleezer&lt;/p&gt;
&lt;p&gt;### 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&amp;#39;s process table.&lt;/p&gt;
&lt;p&gt;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&amp;#39;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.&lt;/p&gt;
&lt;p&gt;This vulnerability affects all users who have configured hook scripts using the `--hook` option.&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### 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&lt;/p&gt;
&lt;p&gt;### 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&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: pleezer&lt;/p&gt;
&lt;p&gt;### 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&amp;#39;s process table.&lt;/p&gt;
&lt;p&gt;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&amp;#39;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.&lt;/p&gt;
&lt;p&gt;This vulnerability affects all users who have configured hook scripts using the `--hook` option.&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;### 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&lt;/p&gt;
&lt;p&gt;### 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&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-472w-7w45-g3w5</guid>
    </item>
  </channel>
</rss>
