<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-15T04:00:49.179583+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2020-35925</id>
    <title>CVE-2020-35925</title>
    <updated>2026-10-15T04:00:49.215250+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in the magnetic crate before 2.0.1 for Rust. MPMCConsumer and MPMCProducer allow cross-thread sending of a non-Send type.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2020-35925"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rustsec-2020-0088</id>
    <title>RUSTSEC-2020-0088 — MPMCConsumer/Producer allows sending non-Send type across threads</title>
    <updated>2026-10-15T04:00:49.215312+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: magnetic</p>
<p>Affected versions of this crate unconditionally implemented `Sync` and `Send` traits for `MPMCConsumer` and `MPMCProducer` types.</p>
<p>This allows users to send types that do not implement `Send` trait across thread boundaries, which can cause a data race.</p>
<p>The flaw was corrected in the 2.0.1 release by adding `T: Send` bound to affected Sync/Send trait implementations.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rustsec-2020-0088"/>
  </entry>
</feed>
