<?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-08T04:43:17.256874+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-36208</id>
    <title>CVE-2020-36208</title>
    <updated>2026-10-08T04:43:17.288249+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in the conquer-once crate before 0.3.2 for Rust. Thread crossing can occur for a non-Send but Sync type, leading to memory corruption.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2020-36208"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3jc5-5hc5-33gj</id>
    <title>GHSA-3jc5-5hc5-33gj — Data races in conquer-once</title>
    <updated>2026-10-08T04:43:17.288300+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: conquer-once</p>
<p>Affected versions of conquer-once implements Sync for its OnceCell type without restricting it to Sendable types.</p>
<p>This allows non-Send but Sync types such as MutexGuard to be sent across threads leading to undefined behavior and memory corruption in concurrent programs.</p>
<p>The issue was fixed by adding a Send constraint to OnceCell.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3jc5-5hc5-33gj"/>
  </entry>
</feed>
