<?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://cve.radiocsirt.org</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, 03 Oct 2026 09:03:51 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-0627 — De multiples vulnérabilités ont été découvertes dans les produits Splunk. Certaines d'entre elles permettent à un attaq…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0627</link>
      <description>certfr-2026-avi-0627</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0627</guid>
    </item>
    <item>
      <title>Withdrawn: CLEANSTART-2026-BK22414 — Security fixes for CVE-2026-25541, ghsa-434x-w66g-qw3r, ghsa-cq8v-f236-94qc applied in versions: 40.0.0-r0</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-bk22414</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: wasmtime&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the wasmtime package. These issues are resolved in later releases. See references for individual vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: wasmtime&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the wasmtime package. These issues are resolved in later releases. See references for individual vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-bk22414</guid>
    </item>
    <item>
      <title>EUVD-2026-267471</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-267471</link>
      <description>EUVD-2026-267471</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-267471</guid>
    </item>
    <item>
      <title>fkie_cve-2026-25541</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-25541</link>
      <description>&lt;p&gt;Bytes is a utility library for working with bytes. From version 1.2.1 to before 1.11.1, Bytes is vulnerable to integer overflow in BytesMut::reserve. In the unique reclaim path of BytesMut::reserve, if the condition &amp;#34;v_capacity &amp;gt;= new_cap + offset&amp;#34; uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB. This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks. This issue has been patched in version 1.11.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Bytes is a utility library for working with bytes. From version 1.2.1 to before 1.11.1, Bytes is vulnerable to integer overflow in BytesMut::reserve. In the unique reclaim path of BytesMut::reserve, if the condition &amp;#34;v_capacity &amp;gt;= new_cap + offset&amp;#34; uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB. This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks. This issue has been patched in version 1.11.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-25541</guid>
    </item>
    <item>
      <title>GHSA-434x-w66g-qw3r — bytes has integer overflow in BytesMut::reserve</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-434x-w66g-qw3r</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: bytes&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;In the unique reclaim path of `BytesMut::reserve`, the condition
```rs
if v_capacity &amp;gt;= new_cap + offset
```
uses an unchecked addition. When `new_cap + offset` overflows `usize` in release builds, this condition may incorrectly pass, causing `self.cap` to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as `spare_capacity_mut()` then trust this corrupted `cap` value and may create out-of-bounds slices, leading to UB.&lt;/p&gt;
&lt;p&gt;This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.&lt;/p&gt;
&lt;p&gt;## PoC&lt;/p&gt;
&lt;p&gt;```rs
use bytes::*;&lt;/p&gt;
&lt;p&gt;fn main() {
    let mut a = BytesMut::from(&amp;amp;b&amp;#34;hello world&amp;#34;[..]);
    let mut b = a.split_off(5);&lt;/p&gt;
&lt;p&gt;// Ensure b becomes the unique owner of the backing storage
    drop(a);&lt;/p&gt;
&lt;p&gt;// Trigger overflow in new_cap + offset inside reserve
    b.reserve(usize::MAX - 6);&lt;/p&gt;
&lt;p&gt;// This call relies on the corrupted cap and may cause UB &amp;amp; HBO
    b.put_u8(b&amp;#39;h&amp;#39;);
}
```&lt;/p&gt;
&lt;p&gt;# Workarounds&lt;/p&gt;
&lt;p&gt;Users of `BytesMut::reserve` are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.&lt;/p&gt;
&lt;p&gt;This vulnerability is also known as [RUSTSEC-2026-0007](https://rustsec.org/advisories/RUSTSEC-2026-0007.html).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: bytes&lt;/p&gt;
&lt;p&gt;# Details&lt;/p&gt;
&lt;p&gt;In the unique reclaim path of `BytesMut::reserve`, the condition
```rs
if v_capacity &amp;gt;= new_cap + offset
```
uses an unchecked addition. When `new_cap + offset` overflows `usize` in release builds, this condition may incorrectly pass, causing `self.cap` to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as `spare_capacity_mut()` then trust this corrupted `cap` value and may create out-of-bounds slices, leading to UB.&lt;/p&gt;
&lt;p&gt;This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.&lt;/p&gt;
&lt;p&gt;## PoC&lt;/p&gt;
&lt;p&gt;```rs
use bytes::*;&lt;/p&gt;
&lt;p&gt;fn main() {
    let mut a = BytesMut::from(&amp;amp;b&amp;#34;hello world&amp;#34;[..]);
    let mut b = a.split_off(5);&lt;/p&gt;
&lt;p&gt;// Ensure b becomes the unique owner of the backing storage
    drop(a);&lt;/p&gt;
&lt;p&gt;// Trigger overflow in new_cap + offset inside reserve
    b.reserve(usize::MAX - 6);&lt;/p&gt;
&lt;p&gt;// This call relies on the corrupted cap and may cause UB &amp;amp; HBO
    b.put_u8(b&amp;#39;h&amp;#39;);
}
```&lt;/p&gt;
&lt;p&gt;# Workarounds&lt;/p&gt;
&lt;p&gt;Users of `BytesMut::reserve` are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.&lt;/p&gt;
&lt;p&gt;This vulnerability is also known as [RUSTSEC-2026-0007](https://rustsec.org/advisories/RUSTSEC-2026-0007.html).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-434x-w66g-qw3r</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-25541 — Bytes is vulnerable to integer overflow in BytesMut::reserve</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-25541</link>
      <description>msrc_CVE-2026-25541</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-25541</guid>
    </item>
    <item>
      <title>openSUSE-RU-2026:21658-1 — Recommended update for sequoia-sq</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-ru-2026:21658-1</link>
      <description>&lt;p&gt;Recommended update for sequoia-sq&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Recommended update for sequoia-sq&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-ru-2026:21658-1</guid>
    </item>
    <item>
      <title>RUSTSEC-2026-0007 — Integer overflow in `BytesMut::reserve`</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2026-0007</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: bytes&lt;/p&gt;
&lt;p&gt;In the unique reclaim path of `BytesMut::reserve`, the condition
```rs
if v_capacity &amp;gt;= new_cap + offset
```
uses an unchecked addition. When `new_cap + offset` overflows `usize` in release builds, this condition may incorrectly pass, causing `self.cap` to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as `spare_capacity_mut()` then trust this corrupted `cap` value and may create out-of-bounds slices, leading to UB.&lt;/p&gt;
&lt;p&gt;This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.&lt;/p&gt;
&lt;p&gt;## PoC&lt;/p&gt;
&lt;p&gt;```rs
use bytes::*;&lt;/p&gt;
&lt;p&gt;fn main() {
    let mut a = BytesMut::from(&amp;amp;b&amp;#34;hello world&amp;#34;[..]);
    let mut b = a.split_off(5);&lt;/p&gt;
&lt;p&gt;// Ensure b becomes the unique owner of the backing storage
    drop(a);&lt;/p&gt;
&lt;p&gt;// Trigger overflow in new_cap + offset inside reserve
    b.reserve(usize::MAX - 6);&lt;/p&gt;
&lt;p&gt;// This call relies on the corrupted cap and may cause UB &amp;amp; HBO
    b.put_u8(b&amp;#39;h&amp;#39;);
}
```&lt;/p&gt;
&lt;p&gt;# Workarounds&lt;/p&gt;
&lt;p&gt;Users of `BytesMut::reserve` are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: bytes&lt;/p&gt;
&lt;p&gt;In the unique reclaim path of `BytesMut::reserve`, the condition
```rs
if v_capacity &amp;gt;= new_cap + offset
```
uses an unchecked addition. When `new_cap + offset` overflows `usize` in release builds, this condition may incorrectly pass, causing `self.cap` to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as `spare_capacity_mut()` then trust this corrupted `cap` value and may create out-of-bounds slices, leading to UB.&lt;/p&gt;
&lt;p&gt;This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.&lt;/p&gt;
&lt;p&gt;## PoC&lt;/p&gt;
&lt;p&gt;```rs
use bytes::*;&lt;/p&gt;
&lt;p&gt;fn main() {
    let mut a = BytesMut::from(&amp;amp;b&amp;#34;hello world&amp;#34;[..]);
    let mut b = a.split_off(5);&lt;/p&gt;
&lt;p&gt;// Ensure b becomes the unique owner of the backing storage
    drop(a);&lt;/p&gt;
&lt;p&gt;// Trigger overflow in new_cap + offset inside reserve
    b.reserve(usize::MAX - 6);&lt;/p&gt;
&lt;p&gt;// This call relies on the corrupted cap and may cause UB &amp;amp; HBO
    b.put_u8(b&amp;#39;h&amp;#39;);
}
```&lt;/p&gt;
&lt;p&gt;# Workarounds&lt;/p&gt;
&lt;p&gt;Users of `BytesMut::reserve` are only affected if integer overflow checks are configured to wrap. When integer overflow is configured to panic, this issue does not apply.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2026-0007</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:22787-1 — Security update for afterburn</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:22787-1</link>
      <description>&lt;p&gt;Security update for afterburn&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for afterburn&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:22787-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-25541</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-25541</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: rust-bytes, Ubuntu:22.04:LTS: rust-bytes, Ubuntu:24.04:LTS: rust-bytes, Ubuntu:25.10: rust-bytes, Ubuntu:26.04:LTS: rust-bytes&lt;/p&gt;
&lt;p&gt;Bytes is a utility library for working with bytes. From version 1.2.1 to before 1.11.1, Bytes is vulnerable to integer overflow in BytesMut::reserve. In the unique reclaim path of BytesMut::reserve, if the condition &amp;#34;v_capacity &amp;gt;= new_cap + offset&amp;#34; uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB. This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks. This issue has been patched in version 1.11.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: rust-bytes, Ubuntu:22.04:LTS: rust-bytes, Ubuntu:24.04:LTS: rust-bytes, Ubuntu:25.10: rust-bytes, Ubuntu:26.04:LTS: rust-bytes&lt;/p&gt;
&lt;p&gt;Bytes is a utility library for working with bytes. From version 1.2.1 to before 1.11.1, Bytes is vulnerable to integer overflow in BytesMut::reserve. In the unique reclaim path of BytesMut::reserve, if the condition &amp;#34;v_capacity &amp;gt;= new_cap + offset&amp;#34; uses an unchecked addition. When new_cap + offset overflows usize in release builds, this condition may incorrectly pass, causing self.cap to be set to a value that exceeds the actual allocated capacity. Subsequent APIs such as spare_capacity_mut() then trust this corrupted cap value and may create out-of-bounds slices, leading to UB. This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks. This issue has been patched in version 1.11.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-25541</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1024 — IBM DataPower Gateway: Schwachstelle ermöglicht Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1024</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in IBM DataPower Gateway ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in IBM DataPower Gateway ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1024</guid>
    </item>
  </channel>
</rss>
