<?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-18T15:56:40.796636+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-36438</id>
    <title>CVE-2020-36438</title>
    <updated>2026-10-18T15:56:40.800072+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in the tiny_future crate before 0.4.0 for Rust. Future&lt;T&gt; does not have bounds on its Send and Sync traits.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2020-36438"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-fg42-vwxx-xx5j</id>
    <title>GHSA-fg42-vwxx-xx5j — Data race in tiny_future</title>
    <updated>2026-10-18T15:56:40.800132+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: tiny_future</p>
<p>tiny_future contains a light-weight implementation of Futures. The Future type it has lacked bound on its Send and Sync traits. This allows for a bug where non-thread safe types such as Cell can be used in Futures and cause data races in concurrent programs. The flaw was corrected in commit `c791919` by adding trait bounds to Future's Send and Sync.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-fg42-vwxx-xx5j"/>
  </entry>
</feed>
