Withdrawn by the publisher.

Affected: CleanStart: wasmtime

Multiple security vulnerabilities affect the wasmtime package. These issues are resolved in later releases. See references for individual vulnerability details.

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 "v_capacity >= 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. 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.

Affected: crates.io: bytes

# Details

In the unique reclaim path of `BytesMut::reserve`, the condition ```rs if v_capacity >= 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.

This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.

## PoC

```rs use bytes::*;

fn main() { let mut a = BytesMut::from(&b"hello world"[..]); let mut b = a.split_off(5);

// Ensure b becomes the unique owner of the backing storage drop(a);

// Trigger overflow in new_cap + offset inside reserve b.reserve(usize::MAX - 6);

// This call relies on the corrupted cap and may cause UB & HBO b.put_u8(b'h'); } ```

# Workarounds

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.

This vulnerability is also known as [RUSTSEC-2026-0007](https://rustsec.org/advisories/RUSTSEC-2026-0007.html).

Recommended update for sequoia-sq

Affected: crates.io: bytes

In the unique reclaim path of `BytesMut::reserve`, the condition ```rs if v_capacity >= 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.

This behavior is observable in release builds (integer overflow wraps), whereas debug builds panic due to overflow checks.

## PoC

```rs use bytes::*;

fn main() { let mut a = BytesMut::from(&b"hello world"[..]); let mut b = a.split_off(5);

// Ensure b becomes the unique owner of the backing storage drop(a);

// Trigger overflow in new_cap + offset inside reserve b.reserve(usize::MAX - 6);

// This call relies on the corrupted cap and may cause UB & HBO b.put_u8(b'h'); } ```

# Workarounds

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.

Security update for afterburn

Affected: 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

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 "v_capacity >= 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. 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.

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in IBM DataPower Gateway ausnutzen, um einen Denial of Service Angriff durchzuführen.