Approved changes feed: RSS · Atom
cpe:2.3:a:tokio-rs:bytes:*:*:*:*:*:rust:*:*
part: a version: * update: *
| Vendor | Tokio Rs (f66f7134-7f98-5eb5-8851-4ebd75b4ec87) |
|---|---|
| Product | Bytes (f04ee767-7500-5313-a36a-436552c70523) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | rust |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/tokio-rs/bytes |
purl2cpe | 2026-06-01 10:17:02.430015 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-25541 |
vulnerable | 2026-06-08 07:53:19.971850 |
Bytes is vulnerable to integer overflow in BytesMut::reserve
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.
Published: 2026-02-04T22:03:53.554Z
Updated: 2026-02-05T15:13:34.031Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.