<?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-08T11:18:53.241888+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-36215</id>
    <title>CVE-2020-36215</title>
    <updated>2026-10-08T11:18:53.261163+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in the hashconsing crate before 1.1.0 for Rust. Because HConsed does not have bounds on its Send trait or Sync trait, memory corruption can occur.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2020-36215"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rustsec-2020-0107</id>
    <title>RUSTSEC-2020-0107 — hashconsing's HConsed lacks Send/Sync bound for its Send/Sync trait.</title>
    <updated>2026-10-08T11:18:53.261216+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: hashconsing</p>
<p>Affected versions of `hashconsing` implements `Send`/`Sync` for its `HConsed` type without restricting it to `Send`able types and `Sync`able types.</p>
<p>This allows non-`Sync` types such as `Cell` to be shared across threads leading to undefined behavior and memory corruption in concurrent programs.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rustsec-2020-0107"/>
  </entry>
</feed>
