Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-25541: Bytes is vulnerable to integer overflow in BytesMut::reserve

Noroxi assessment

Priority: Monitor (action score 22/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.60% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: tokio-rs bytes 1.11.1; azl3 rust-afterburn 5.8.2-1 on Azure Linux 3.0 5.8.2-2; azl3 rust-afterburn 5.8.2-2 on Azure Linux 3.0 5.8.2-2.

Low priority for now. Upgrade to tokio-rs bytes 1.11.1; azl3 rust-afterburn 5.8.2-1 on Azure Linux 3.0 5.8.2-2; azl3 rust-afterburn 5.8.2-2 on Azure Linux 3.0 5.8.2-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v4.0—Proof of concept Fix available
Published
Feb 4, 2026
Updated
Jun 17, 2026
EPSS
0.6% · 48th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.6%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
5.5
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-25541

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for tokio-rs records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
tokio-rsbytes

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • tokio-rs bytes1.2.1 and later · before 1.11.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • tokio-rs bytes

    • >= 1.2.1, < 1.11.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
crates.iobytesfrom 1.2.1 · before 1.11.11.11.1
Debian:12rust-bytesfrom 0—
Debian:14rust-bytesbefore 1.11.1-11.11.1-1
openSUSE:Leap 16.0afterburnbefore 5.10.0.git73.b97f772-160000.1.15.10.0.git73.b97f772-160000.1.1
openSUSE:Leap 16.0agamabefore 17+699.92879916c-160000.13.117+699.92879916c-160000.13.1
openSUSE:Leap 16.0aws-nitro-enclaves-clibefore 1.5.0~git0.2950b36-160000.1.11.5.0~git0.2950b36-160000.1.1
openSUSE:Leap 16.0forgejo-clibefore 0.6.0-bp160.1.10.6.0-bp160.1.1
openSUSE:Leap 16.0git-cliffbefore 2.13.1-bp160.1.12.13.1-bp160.1.1
openSUSE:Leap 16.0gitoxidebefore 0.56.0-bp160.1.10.56.0-bp160.1.1
openSUSE:Leap 16.0gstreamer-devtoolsbefore 1.26.7-160000.2.11.26.7-160000.2.1
openSUSE:Leap 16.0kak-lspbefore 21.0.2-bp160.1.121.0.2-bp160.1.1
openSUSE:Leap 16.0nm-configuratorbefore 0.3.5-160000.1.10.3.5-160000.1.1
openSUSE:Leap 16.0rustupbefore 1.29.1~0-160000.1.11.29.1~0-160000.1.1
openSUSE:Leap 16.0sccachebefore 0.18.0~2-160000.1.10.18.0~2-160000.1.1
openSUSE:Leap 16.0sequoia-sqbefore 1.4.0-bp160.1.11.4.0-bp160.1.1
openSUSE:Leap 16.0shadowsocks-libevbefore 3.3.6-bp160.3.13.3.6-bp160.3.1
openSUSE:Leap 16.0shadowsocks-rustbefore 1.25.0-bp160.1.11.25.0-bp160.1.1
openSUSE:Leap 16.0supergfxctlbefore 1762634235.5d503b1-bp160.1.11762634235.5d503b1-bp160.1.1
openSUSE:Leap 16.0waylyricsbefore 0.4.0-bp160.1.10.4.0-bp160.1.1
openSUSE:Tumbleweedafterburnbefore 5.10.0.git73.b97f772-1.15.10.0.git73.b97f772-1.1
openSUSE:Tumbleweedagamabefore 24+0.a836cced5-54.124+0.a836cced5-54.1
openSUSE:Tumbleweedaws-efs-utilsbefore 3.2.0-1.13.2.0-1.1
openSUSE:Tumbleweedaws-nitro-enclaves-clibefore 1.5.0~git0.2950b36-1.11.5.0~git0.2950b36-1.1
openSUSE:Tumbleweedcargo-auditbefore 0.22.2~git0.281452c-2.10.22.2~git0.281452c-2.1

+33

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
tokio-rs bytes1.11.1 · descriptionVendor (CNA)
azl3 rust-afterburn 5.8.2-1 on Azure Linux 3.05.8.2-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 rust-afterburn 5.8.2-2 on Azure Linux 3.05.8.2-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 trident 0.21.0-1 on Azure Linux 3.00.22.0-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
crates.io:bytes1.11.1Package registry (OSV)
debian:rust-bytes1.11.1-1 · Debian:14Package registry (OSV)
opensuse:afterburn5.10.0.git73.b97f772-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:aws-efs-utils3.2.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:cargo-audit0.22.2~git0.281452c-2.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:cargo-c0.10.23-2.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:git-cliff2.13.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:gitoxide0.56.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:kak-lsp21.0.2-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:nm-configurator0.3.5-2.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:obs-service-cargo7.2.2-2.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:rustup1.29.0~0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:sequoia-sq1.4.0-bp160.1.1 · openSUSE:Leap 16.0Package registry (OSV)
opensuse:wild0.10.0-2.1 · openSUSE:TumbleweedPackage registry (OSV)
suse:afterburn5.10.0.git73.b97f772-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:agama17+699.92879916c-160000.13.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:aws-nitro-enclaves-cli1.5.0~git0.2950b36-160000.1.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:gstreamer-devtools1.26.7-160000.2.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:nm-configurator0.3.5-160000.1.1 · SUSE:Linux Micro 6.2Package registry (OSV)
suse:rustup1.29.1~0-160000.1.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:sccache0.17.0~1-150600.10.14.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:sccache0.18.0~2-160000.1.1 · SUSE:Linux Enterprise Server 16.0Package registry (OSV)
suse:snpguest0.3.2-150600.3.14.1 · SUSE:Linux Enterprise Server 15 SP6-LTSSPackage registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:12026-06-22

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+137 d
  3. TodayNov 2, 2026+271 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

Weakness class (CWE)

CWE-680 · Integer Overflow to Buffer Overflow

CVSS vector

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records