<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 18 Oct 2026 05:02:45 +0000</lastBuildDate>
    <item>
      <title>RUSTSEC-2025-0132 — `Reader::open_mmap` unsoundly marks unsafe memmap operation as safe</title>
      <link>https://db.gcve.eu/vuln/rustsec-2025-0132</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: maxminddb&lt;/p&gt;
&lt;p&gt;maxminddb prior to version 0.27 declared `Reader::open_mmap` as safe 
despite wrapping an inherently unsafe memmap2 operation with no
extra step done to guarantee safety. This could have led to undefined
behaviour if the file were to be modified on disk while the memory map
was still active.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: maxminddb&lt;/p&gt;
&lt;p&gt;maxminddb prior to version 0.27 declared `Reader::open_mmap` as safe 
despite wrapping an inherently unsafe memmap2 operation with no
extra step done to guarantee safety. This could have led to undefined
behaviour if the file were to be modified on disk while the memory map
was still active.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rustsec-2025-0132</guid>
    </item>
  </channel>
</rss>
