<?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-09T18:14:37.736637+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-36461</id>
    <title>CVE-2020-36461</title>
    <updated>2026-10-09T18:14:37.770220+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in the noise_search crate through 2020-12-10 for Rust. There are unconditional implementations of Send and Sync for MvccRwLock.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2020-36461"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-wxjf-9f4g-3v44</id>
    <title>GHSA-wxjf-9f4g-3v44 — Data races in noise_search</title>
    <updated>2026-10-09T18:14:37.770277+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: noise_search</p>
<p>Affected versions of the `noise_search` crate unconditionally implement Send/Sync for `MvccRwLock`.
This can lead to data races when types that are either `!Send` or `!Sync` (e.g. `Rc&lt;T&gt;`, `Arc&lt;Cell&lt;_&gt;&gt;`) are contained inside `MvccRwLock` and sent across thread boundaries. The data races can potentially lead to memory corruption (as demonstrated in the PoC from the original report issue).</p>
<p>Also, safe APIs of `MvccRwLock` allow aliasing violations by allowing `&amp;T` and `LockResult&lt;MutexGuard&lt;Box&lt;T&gt;&gt;&gt;` to co-exist in conflicting lifetime regions. The APIs of `MvccRwLock` should either be marked as `unsafe` or `MbccRwLock` should be changed to private or pub(crate).</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-wxjf-9f4g-3v44"/>
  </entry>
</feed>
