<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T19:46:31.268238+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cve-2026-41678</id>
    <title>CVE-2026-41678 — rust-openssl: Incorrect bounds assertion in aes key wrap</title>
    <updated>2026-09-28T19:46:31.283256+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> rust-openssl</p>
<p>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 &lt;= in_.len(), but this condition is reversed. The intended invariant is out.len() &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.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-41678"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-8c75-8mhr-p7r9</id>
    <title>GHSA-8c75-8mhr-p7r9 — rust-openssl has incorrect bounds assertion in aes key wrap</title>
    <updated>2026-09-28T19:46:31.283369+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: openssl</p>
<p>### Summary
``aes::unwrap_key()`` has an incorrect bounds assertion on the out buffer size, which can lead to out-of-bounds write.</p>
<p>### Details
``aes::unwrap_key()`` contains an incorrect assertion: it checks that `out.len() + 8 &lt;= in_.len()`, but this condition is reversed. The intended invariant is `out.len() &gt;= in_.len() - 8`, ensuring the output buffer is large enough.</p>
<p>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.</p>
<p>### Impact
Vulnerable applications using AES keywrap and allowing attacker controlled buffer sizes could have an attacker trigger an out-of-bounds write.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-8c75-8mhr-p7r9"/>
  </entry>
</feed>
