<?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>Mon, 28 Sep 2026 19:46:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-41678 — rust-openssl: Incorrect bounds assertion in aes key wrap</title>
      <link>https://db.gcve.eu/vuln/cve-2026-41678</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rust-openssl&lt;/p&gt;
&lt;p&gt;rust-openssl provides OpenSSL bindings for the Rust programming language.  From  to before 0.10.78, aes::unwrap_key() contains an incorrect assertion: it checks that out.len() + 8 &amp;lt;= in_.len(), but this condition is reversed. The intended invariant is out.len() &amp;gt;= in_.len() - 8, ensuring the output buffer is large enough. Because of the inverted check, the function only accepts buffers at or below the minimum required size and rejects larger ones. If a smaller buffer is provided the function will write past the end of out by in_.len() - 8 - out.len() bytes, causing an out-of-bounds write from a safe public function. This vulnerability is fixed in 0.10.78.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rust-openssl&lt;/p&gt;
&lt;p&gt;rust-openssl provides OpenSSL bindings for the Rust programming language.  From  to before 0.10.78, aes::unwrap_key() contains an incorrect assertion: it checks that out.len() + 8 &amp;lt;= in_.len(), but this condition is reversed. The intended invariant is out.len() &amp;gt;= in_.len() - 8, ensuring the output buffer is large enough. Because of the inverted check, the function only accepts buffers at or below the minimum required size and rejects larger ones. If a smaller buffer is provided the function will write past the end of out by in_.len() - 8 - out.len() bytes, causing an out-of-bounds write from a safe public function. This vulnerability is fixed in 0.10.78.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-41678</guid>
    </item>
    <item>
      <title>GHSA-8c75-8mhr-p7r9 — rust-openssl has incorrect bounds assertion in aes key wrap</title>
      <link>https://db.gcve.eu/vuln/ghsa-8c75-8mhr-p7r9</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: openssl&lt;/p&gt;
&lt;p&gt;### Summary
``aes::unwrap_key()`` has an incorrect bounds assertion on the out buffer size, which can lead to out-of-bounds write.&lt;/p&gt;
&lt;p&gt;### Details
``aes::unwrap_key()`` contains an incorrect assertion: it checks that `out.len() + 8 &amp;lt;= in_.len()`, but this condition is reversed. The intended invariant is `out.len() &amp;gt;= in_.len() - 8`, ensuring the output buffer is large enough.&lt;/p&gt;
&lt;p&gt;Because of the inverted check, the function only accepts buffers at or below the minimum required size and rejects larger ones. If a smaller buffer is provided the function will write past the end of `out` by `in_.len() - 8 - out.len()` bytes, causing an out-of-bounds write from a safe public function.&lt;/p&gt;
&lt;p&gt;### Impact
Vulnerable applications using AES keywrap and allowing attacker controlled buffer sizes could have an attacker trigger an out-of-bounds write.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: openssl&lt;/p&gt;
&lt;p&gt;### Summary
``aes::unwrap_key()`` has an incorrect bounds assertion on the out buffer size, which can lead to out-of-bounds write.&lt;/p&gt;
&lt;p&gt;### Details
``aes::unwrap_key()`` contains an incorrect assertion: it checks that `out.len() + 8 &amp;lt;= in_.len()`, but this condition is reversed. The intended invariant is `out.len() &amp;gt;= in_.len() - 8`, ensuring the output buffer is large enough.&lt;/p&gt;
&lt;p&gt;Because of the inverted check, the function only accepts buffers at or below the minimum required size and rejects larger ones. If a smaller buffer is provided the function will write past the end of `out` by `in_.len() - 8 - out.len()` bytes, causing an out-of-bounds write from a safe public function.&lt;/p&gt;
&lt;p&gt;### Impact
Vulnerable applications using AES keywrap and allowing attacker controlled buffer sizes could have an attacker trigger an out-of-bounds write.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-8c75-8mhr-p7r9</guid>
    </item>
  </channel>
</rss>
