<?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>Sat, 10 Oct 2026 12:03:52 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-7631</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-7631</link>
      <description>EUVD-2026-7631</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-7631</guid>
    </item>
    <item>
      <title>fkie_cve-2023-6180</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-6180</link>
      <description>&lt;p&gt;The tokio-boring library in version 4.0.0 is affected by a memory leak issue that can lead to excessive resource consumption and potential DoS by resource exhaustion. The set_ex_data function used by the library did not deallocate memory used by pre-existing data in memory each time after completing a TLS connection causing the program to consume more resources with each new connection.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;The tokio-boring library in version 4.0.0 is affected by a memory leak issue that can lead to excessive resource consumption and potential DoS by resource exhaustion. The set_ex_data function used by the library did not deallocate memory used by pre-existing data in memory each time after completing a TLS connection causing the program to consume more resources with each new connection.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-6180</guid>
    </item>
    <item>
      <title>GHSA-pjrj-h4fg-6gm4 — tokio-boring vulnerable to resource exhaustion via memory leak</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pjrj-h4fg-6gm4</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: tokio-boring&lt;/p&gt;
&lt;p&gt;### Impact
The tokio-boring library in version 4.0.0 is affected by a memory leak issue that can lead to excessive resource consumption and potential DoS by resource exhaustion. The `set_ex_data` function used by the library did not deallocate memory used by pre-existing data in memory each time after completing a TLS connection causing the program to consume more resources with each new connection.&lt;/p&gt;
&lt;p&gt;### Patches
The issue is fixed in version 4.1.0 of tokio-boring.&lt;/p&gt;
&lt;p&gt;### References
[CVE-2023-6180 at cve.org](https://www.cve.org/CVERecord?id=CVE-2023-6180)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: tokio-boring&lt;/p&gt;
&lt;p&gt;### Impact
The tokio-boring library in version 4.0.0 is affected by a memory leak issue that can lead to excessive resource consumption and potential DoS by resource exhaustion. The `set_ex_data` function used by the library did not deallocate memory used by pre-existing data in memory each time after completing a TLS connection causing the program to consume more resources with each new connection.&lt;/p&gt;
&lt;p&gt;### Patches
The issue is fixed in version 4.1.0 of tokio-boring.&lt;/p&gt;
&lt;p&gt;### References
[CVE-2023-6180 at cve.org](https://www.cve.org/CVERecord?id=CVE-2023-6180)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pjrj-h4fg-6gm4</guid>
    </item>
    <item>
      <title>gsd-2023-6180</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-6180</link>
      <description>gsd-2023-6180</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-6180</guid>
    </item>
  </channel>
</rss>
