<?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://127.0.0.1:10001/rss/recent/osv_rustsec/10</id>
  <title>Most recent entries from osv_rustsec</title>
  <updated>2026-11-19T19:22:45.680988+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" 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://127.0.0.1:10001/vuln/rustsec-2026-0582</id>
    <title>RUSTSEC-2026-0582 — On maps of `u16::MAX` elements, `IndexMap::insert` could lead to a broken invariant</title>
    <updated>2026-11-19T08:55:47+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: heapless</p>
<p>Note that this required filling up the map and having the last item inserted to hash to `u16::MAX`. It is therefore very unlikely to be reachable in a real-world scenario.</p>
<p>Reported by [8rsrf7](https://github.com/8rsrf7).</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rustsec-2026-0582"/>
    <published>2026-11-18T12:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rustsec-2026-0581</id>
    <title>RUSTSEC-2026-0581 — `Deque::make_contiguous` could lead to broken invariants</title>
    <updated>2026-11-19T08:55:47+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: heapless</p>
<p>In some branches, `Deque::make_contiguous` set the `back` value to either `0` or `N` when it shouldn't, leading to broken invariants and out-of-bounds writes.</p>
<p>Reported by [DRMacIver](https://github.com/DRMacIver) and [https://github.com/MJUCOM](https://github.com/MJUCOM).</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rustsec-2026-0581"/>
    <published>2026-11-18T12:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rustsec-2026-0580</id>
    <title>RUSTSEC-2026-0580 — The treiber stack implementation in heapless had a race condition</title>
    <updated>2026-11-19T08:55:47+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: heapless</p>
<p>In the affected versions, it was possible for two threads or execution contexts running concurrently to race, causing one to read out of a pointer that had been invalidated by another execution context.</p>
<p>Reported by [Jacob Finkelman](https://github.com/Eh2406).</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rustsec-2026-0580"/>
    <published>2026-11-18T12:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rustsec-2026-0579</id>
    <title>RUSTSEC-2026-0579 — The `Deque` implementation from `TryFrom` was wrong when the `Deque` ended up full</title>
    <updated>2026-11-19T08:55:47+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: heapless</p>
<p>If the array passed to `Deque::try_from` was as long as the capacity of the `Deque`, it would lead to a invalid state.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rustsec-2026-0579"/>
    <published>2026-11-18T12:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rustsec-2026-0578</id>
    <title>RUSTSEC-2026-0578 — `SortedLinkedList::zeroize` lead to an inconsistent state</title>
    <updated>2026-11-19T08:55:47+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: heapless</p>
<p>The `Zeroize` implementation of `SortedLinkedList` did not properly re-initialize the linked list, leading to broken invariants and memorry corruption.</p>
<p>Reported by [Jacob Finkelman](https://github.com/Eh2406).</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rustsec-2026-0578"/>
    <published>2026-11-18T12:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rustsec-2026-0577</id>
    <title>RUSTSEC-2026-0577 — Panicking `Drop` implementation could lead to UB</title>
    <updated>2026-11-19T08:55:47+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: heapless</p>
<p>Multiple functions dropped generic parameters but didn't properly handle the unwinding case, leading to broken invariants.</p>
<p>Reported by [tooson9010-spec](https://github.com/tooson9010-spec) and [Evian-Zhang](https://github.com/Evian-Zhang).</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rustsec-2026-0577"/>
    <published>2026-11-18T12:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rustsec-2026-0576</id>
    <title>RUSTSEC-2026-0576 — `IndexMap::truncate` could lead to an inconsistent state</title>
    <updated>2026-11-19T08:55:47+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: heapless</p>
<p>`IndexMap::truncate` was not rebuilding indices when it should, leading to an inconsistent state and memory corruption.</p>
<p>Reported by [Jacob Finkelman](https://github.com/Eh2406).</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rustsec-2026-0576"/>
    <published>2026-11-18T12:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rustsec-2026-0575</id>
    <title>RUSTSEC-2026-0575 — `Spsc::peek` used `Relaxed` ordering where it should have use `Acquire`</title>
    <updated>2026-11-19T08:55:47+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: heapless</p>
<p>This could lead to UB through a race condition.</p>
<p>Reported by [Jacob Finkelman](https://github.com/Eh2406).</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rustsec-2026-0575"/>
    <published>2026-11-18T12:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rustsec-2026-0574</id>
    <title>RUSTSEC-2026-0574 — `FindMutView::pop` after mutating the value would lead to a use after free</title>
    <updated>2026-11-19T08:55:47+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: heapless</p>
<p>Reported by [Jacob Finkelman](https://github.com/Eh2406).</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rustsec-2026-0574"/>
    <published>2026-11-18T12:00:00+00:00</published>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rustsec-2026-0565</id>
    <title>RUSTSEC-2026-0565 — Unbounded buffering of an SMTP reply allows a malicious server to exhaust memory</title>
    <updated>2026-11-18T09:14:42+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: lettre</p>
<p>A malicious or compromised server can send a reply line that never ends, which
the client buffers until memory runs out. A reply made of many short lines also
keeps a CPU core busy: for a few seconds per reply since 0.11.22, for as long
as the server wants before it.</p>
<p>Applications that connect only to a trusted server over implicit TLS are not
exposed; the risk applies to clients that may connect to untrusted servers, or
that use `STARTTLS` or no TLS, where a man-in-the-middle can forge the reply.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rustsec-2026-0565"/>
    <published>2026-11-17T12:00:00+00:00</published>
  </entry>
</feed>
