<?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://vulnerability.circl.lu</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>Wed, 07 Oct 2026 05:49:25 +0000</lastBuildDate>
    <item>
      <title>RUSTSEC-2026-0116 — Improper check of an invariant resulting in incorrect bounds checks</title>
      <link>https://vulnerability.circl.lu/vuln/rustsec-2026-0116</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: imageproc&lt;/p&gt;
&lt;p&gt;A bounds verification of a slice storage of a 2-dimensional matrix&amp;#39;s
coefficients (a kernel) would compare the total size against the product of
individual dimensions. This would erroneously cast *after* the multiplication
and consequently fail to detect possible violations when overflow occurs.&lt;/p&gt;
&lt;p&gt;Afterwards, the individual sizes were trusted to properly constrain coordinates
within the matrix to indices valid for the underlying storage. With a crafted
`Kernel` object, certain combinations of coordinates could then cause an
out-of-bounds access in an `unsafe` function while fulfilling its documented
preconditions. The kernel value could be passed to library functions that
trusted the preconditions and then performed such reads.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: imageproc&lt;/p&gt;
&lt;p&gt;A bounds verification of a slice storage of a 2-dimensional matrix&amp;#39;s
coefficients (a kernel) would compare the total size against the product of
individual dimensions. This would erroneously cast *after* the multiplication
and consequently fail to detect possible violations when overflow occurs.&lt;/p&gt;
&lt;p&gt;Afterwards, the individual sizes were trusted to properly constrain coordinates
within the matrix to indices valid for the underlying storage. With a crafted
`Kernel` object, certain combinations of coordinates could then cause an
out-of-bounds access in an `unsafe` function while fulfilling its documented
preconditions. The kernel value could be passed to library functions that
trusted the preconditions and then performed such reads.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rustsec-2026-0116</guid>
    </item>
  </channel>
</rss>
