<?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>Sat, 21 Nov 2026 09:55:39 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-92613</title>
      <link>https://db.gcve.eu/vuln/cve-2026-92613</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Eclipse Foundation Eclipse iceoryx™&lt;/p&gt;
&lt;p&gt;In Eclipse iceoryx-rs, versions 0.0.11 to 0.0.13 and 0.1.0 as well as on the latest main branch.&lt;/p&gt;
&lt;p&gt;`SampleReceiver::&amp;lt;T&amp;gt;::take()` and `Sample::&amp;lt;T&amp;gt;::deref()` are safe functions that hand the caller a `&amp;amp;T` pointing at a chunk written by another iceoryx process, but the subscriber path neither requires `T: ShmSend` nor verifies that the received chunk is at least `size_of::&amp;lt;T&amp;gt;()` bytes / `align_of::&amp;lt;T&amp;gt;()`-aligned. A peer process that publishes an undersized chunk, or any chunk at all when the subscriber chose a pointer-bearing `T`, drives a `#![forbid(unsafe_code)]` subscriber into out-of-bounds reads of adjacent shared-memory chunks or dereference of a publisher-controlled pointer.&lt;/p&gt;
&lt;p&gt;Resolution:&lt;/p&gt;
&lt;p&gt;It will not be fixed since this is a known limitation in iceoryx as it is the users responsibility to specify the same data type on sender and receiver side.&lt;/p&gt;
&lt;p&gt;[iceoryx2](https://github.com/eclipse-iceoryx/iceoryx2) is the successor of iceoryx-rs where the API is designed to prevent this by default.&lt;/p&gt;
&lt;p&gt;It is strongly recommended to migrate to iceoryx2 which is actively maintained and receives security support.&lt;/p&gt;
&lt;p&gt;The iceoryx-rs package has officially reached End-of-life and will not receive any features, bugfixes or security fixes.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Eclipse Foundation Eclipse iceoryx™&lt;/p&gt;
&lt;p&gt;In Eclipse iceoryx-rs, versions 0.0.11 to 0.0.13 and 0.1.0 as well as on the latest main branch.&lt;/p&gt;
&lt;p&gt;`SampleReceiver::&amp;lt;T&amp;gt;::take()` and `Sample::&amp;lt;T&amp;gt;::deref()` are safe functions that hand the caller a `&amp;amp;T` pointing at a chunk written by another iceoryx process, but the subscriber path neither requires `T: ShmSend` nor verifies that the received chunk is at least `size_of::&amp;lt;T&amp;gt;()` bytes / `align_of::&amp;lt;T&amp;gt;()`-aligned. A peer process that publishes an undersized chunk, or any chunk at all when the subscriber chose a pointer-bearing `T`, drives a `#![forbid(unsafe_code)]` subscriber into out-of-bounds reads of adjacent shared-memory chunks or dereference of a publisher-controlled pointer.&lt;/p&gt;
&lt;p&gt;Resolution:&lt;/p&gt;
&lt;p&gt;It will not be fixed since this is a known limitation in iceoryx as it is the users responsibility to specify the same data type on sender and receiver side.&lt;/p&gt;
&lt;p&gt;[iceoryx2](https://github.com/eclipse-iceoryx/iceoryx2) is the successor of iceoryx-rs where the API is designed to prevent this by default.&lt;/p&gt;
&lt;p&gt;It is strongly recommended to migrate to iceoryx2 which is actively maintained and receives security support.&lt;/p&gt;
&lt;p&gt;The iceoryx-rs package has officially reached End-of-life and will not receive any features, bugfixes or security fixes.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-92613</guid>
    </item>
  </channel>
</rss>
