<?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, 14 Oct 2026 22:34:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2020-36454</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2020-36454</link>
      <description>&lt;p&gt;An issue was discovered in the parc crate through 2020-11-14 for Rust. LockWeak&amp;lt;T&amp;gt; has an unconditional implementation of Send without trait bounds on T.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in the parc crate through 2020-11-14 for Rust. LockWeak&amp;lt;T&amp;gt; has an unconditional implementation of Send without trait bounds on T.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2020-36454</guid>
    </item>
    <item>
      <title>GHSA-29v7-3v4c-gf38 — Data races in parc</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-29v7-3v4c-gf38</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: parc&lt;/p&gt;
&lt;p&gt;In the affected versions of this crate, LockWeak&amp;lt;T&amp;gt; unconditionally implemented Send with no trait bounds on T. LockWeak&amp;lt;T&amp;gt; doesn&amp;#39;t own T and only provides &amp;amp;T. This allows concurrent access to a non-Sync T, which can cause undefined behavior like data races.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: parc&lt;/p&gt;
&lt;p&gt;In the affected versions of this crate, LockWeak&amp;lt;T&amp;gt; unconditionally implemented Send with no trait bounds on T. LockWeak&amp;lt;T&amp;gt; doesn&amp;#39;t own T and only provides &amp;amp;T. This allows concurrent access to a non-Sync T, which can cause undefined behavior like data races.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-29v7-3v4c-gf38</guid>
    </item>
  </channel>
</rss>
