CVE-2026-24889: soroban-sdk has overflow in Bytes :slice, Vec::slice, GenRange::gen_range For U64 Vulnerability

MODERATE
Advisory Identifier: GHSA-96xm-fv9w-pf3f
CVSS 5.3
CWE-190
Published
Advisory Summary

CVE-2026-24889 is a MODERATE (CVSS 5.3) :slice, vec::slice, genrange::gen_range for u64 vulnerability (CWE-190: Integer Overflow or Wraparound) affecting soroban-sdk has overflow in Bytes libraries in the crates.io ecosystem. The issue involves :slice, vec::slice, genrange::gen_range for u64. Remediation is available by upgrading affected packages to version 25.0.2, 23.5.1, 22.0.9.

CVE-2026-24889 at a Glance

CVE Identifier CVE-2026-24889
GHSA Identifier GHSA-96xm-fv9w-pf3f
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-190: Integer Overflow or Wraparound
Affected Product soroban-sdk has overflow in Bytes
Package Ecosystem crates.io
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-24889

To remediate this vulnerability, upgrade all affected soroban-sdk has overflow in Bytes dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

soroban-sdk fixed: 25.0.2
Upgrade soroban-sdk to 25.0.2
soroban-sdk fixed: 23.5.1
Upgrade soroban-sdk to 23.5.1
soroban-sdk fixed: 22.0.9
Upgrade soroban-sdk to 22.0.9
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for soroban-sdk

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-24889, inspect your project dependencies for soroban-sdk has overflow in Bytes:

inspect dependencies for soroban-sdk

Analyze the terminal output to locate any version of soroban-sdk has overflow in Bytes in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 25.0.2), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-190: Integer Overflow or Wraparound, where the product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. this occurs when an integer value is incremented to a value that is too large to store in the associated representation. when this occurs, the value may become a very small or negative number. In soroban-sdk has overflow in Bytes, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Arithmetic overflow can be triggered in the `Bytes::slice`, `Vec::slice`, and `Prng::gen_range` (for `u64`) methods in the `soroban-sdk` in versions prior to and including `25.0.1`. Contracts that pass user-controlled or computed range bounds to `Bytes::slice`, `Vec::slice`, or `Prng::gen_range` may silently operate on incorrect data ranges or generate random numbers from an unintended range, potentially resulting in corrupted contract state. Note that the best practice when using the `soroban-sdk` and building Soroban contracts is to always enable `overflow-checks = true`. The `stellar contract init` tool that prepares the boiler plate for a Soroban contract, as well as all examples and docs, encourage the use of configuring `overflow-checks = true` on `release` profiles so that these arithmetic operations fail rather than silently wrap. Contracts are only impacted if they use `overflow-checks = false` either explicitly or implicitly. It is anticipated the majority of contracts could not be impacted because the best practice encouraged by tooling is to enable `overflow-checks`. ### Detail When compiled with `overflow-checks = false` (the default for release builds), the bare arithmetic in those functions silently wraps on boundary values like `u32::MAX` or `u64::MAX`. This causes the range passed to the host to differ from the caller's intent: `Bytes::slice`: - `Bytes::slice(0..=u32::MAX)` — end `u32::MAX + 1` wraps to `0`, producing `slice(0..0)` returning empty instead of the full range. - `Bytes::slice((Bound::Excluded(u32::MAX), Bound::Unbounded))` — start `u32::MAX + 1` wraps to `0`, producing `slice(0..)` instead of an empty/invalid range. `Vec::slice`: - `Vec::slice(0..=u32::MAX)` — same as `Bytes`, end wraps to `0`, returning empty. - `Vec::slice((Bound::Excluded(u32::MAX), Bound::Unbounded))` — same as `Bytes`, start wraps to `0`. `Prng::gen_range`: - `Prng::gen_range((Bound::Unbounded, Bound::Excluded(0)))` — end `0 - 1` wraps to `u64::MAX`, producing range `0..=u64::MAX` instead of an empty/invalid range. - `Prng::gen_range((Bound::Excluded(u64::MAX), Bound::Unbounded))` — start `u64::MAX + 1` wraps to `0`, producing range `0..=u64::MAX` instead of an empty/invalid range. Note that some cases where the overflow was permitted and wrapped on the guest side are caught by the Soroban Env Host and cause a trap host side with error `HostError: Error(Object, IndexBounds)` `object index out of bounds`, because the wrapped values create invalid inputs: - `Bytes::slice(u32::MAX..=u32::MAX)` — both start `u32::MAX + 1` and end `u32::MAX + 1` wrap to `0`, producing `slice(0..0)`. - `Vec::slice(u32::MAX..=u32::MAX)` — same as `Bytes`, both wrap to `0`. ### Patches The fix replaces bare arithmetic with `checked_add` / `checked_sub`, ensuring overflow traps regardless of the `overflow-checks` profile setting. ### Workarounds Contract workspaces can be configured with the following profile to enable overflow checks on the arithmetic operations. This is the best practice when developing Soroban contracts, and the default if using the contract boilerplate generated using `stellar contract init`: ```toml [profile.release] overflow-checks = true ``` Alternatively, contracts can validate range bounds before passing them to `slice` or `gen_range` to ensure the conversions cannot overflow: - Do not pass `Bound::Excluded(u32::MAX)` or `Bound::Included(u32::MAX)` to `Bytes::slice` or `Vec::slice`. - Do not pass `Bound::Excluded(u64::MAX)` as a start bound or `Bound::Excluded(0)` as an end bound to `Prng::gen_range::<u64>`. ### References - https://github.com/stellar/rs-soroban-sdk/pull/1703 - https://github.com/stellar/rs-soroban-sdk/releases/tag/v25.0.2 - https://github.com/stellar/rs-soroban-sdk/releases/tag/v23.5.1 - https://github.com/stellar/rs-soroban-sdk/releases/tag/v22.0.9

CVE-2026-24889 Affected soroban-sdk has overflow in Bytes Versions

3 component(s)
Fixed Versions:
25.0.223.5.122.0.9
Product / Package Ecosystem Affected Versions Fixed Version
soroban-sdk
crates.io
≥ 25.0.0
< 25.0.2
25.0.2
soroban-sdk
crates.io
≥ 23.0.0
< 23.5.1
23.5.1
soroban-sdk
crates.io
< 22.0.9
22.0.9

References

Frequently Asked Questions

What is CVE-2026-24889?
CVE-2026-24889 is a security vulnerability in soroban-sdk has overflow in Bytes involving :slice, Vec::slice, GenRange::gen_range for u64 under CWE-190: Integer Overflow or Wraparound.
Which soroban-sdk has overflow in Bytes versions are affected?
Affected versions include releases prior to 25.0.2, 23.5.1, 22.0.9 across affected packages: soroban-sdk.
What version fixes CVE-2026-24889?
Upgrading to 25.0.2, 23.5.1, 22.0.9 (or the latest patched release for your respective branch) resolves the vulnerability.
Is soroban-sdk affected?
Yes, soroban-sdk is affected in releases prior to 25.0.2, 23.5.1, 22.0.9. Upgrade your dependency to 25.0.2, 23.5.1, 22.0.9 or later.
What is the CVSS score of CVE-2026-24889?
CVE-2026-24889 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2026-24889?
CVE-2026-24889 is classified under CWE-190: Integer Overflow or Wraparound (The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.).
How can I check crates.io dependencies for CVE-2026-24889?
Run the dependency tree command: 'inspect dependencies for soroban-sdk'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-96xm-fv9w-pf3f",
  "modified" : "2026-01-29T03:56:38Z",
  "published" : "2026-01-28T22:20:35Z",
  "aliases" : [ "CVE-2026-24889" ],
  "summary" : "soroban-sdk has overflow in Bytes::slice, Vec::slice, GenRange::gen_range for u64",
  "details" : "### Impact\n\nArithmetic overflow can be triggered in the `Bytes::slice`, `Vec::slice`, and `Prng::gen_range` (for `u64`) methods in the `soroban-sdk` in versions prior to and including `25.0.1`.\n\nContracts that pass user-controlled or computed range bounds to `Bytes::slice`, `Vec::slice`, or `Prng::gen_range` may silently operate on incorrect data ranges or generate random numbers from an unintended range, potentially resulting in corrupted contract state.\n\nNote that the best practice when using the `soroban-sdk` and building Soroban contracts is to always enable `overflow-checks = true`. The `stellar contract init` tool that prepares the boiler plate for a Soroban contract, as well as all examples and docs, encourage the use of configuring `overflow-checks = true` on `release` profiles so that these arithmetic operations fail rather than silently wrap. Contracts are only impacted if they use `overflow-checks = false` either explicitly or implicitly. It is anticipated the majority of contracts could not be impacted because the best practice encouraged by tooling is to enable `overflow-checks`.\n\n### Detail\n\nWhen compiled with `overflow-checks = false` (the default for release builds), the bare arithmetic in those functions silently wraps on boundary values like `u32::MAX` or `u64::MAX`. This causes the range passed to the host to differ from the caller's intent:\n\n`Bytes::slice`:\n- `Bytes::slice(0..=u32::MAX)` — end `u32::MAX + 1` wraps to `0`, producing `slice(0..0)` returning empty instead of the full range.\n- `Bytes::slice((Bound::Excluded(u32::MAX), Bound::Unbounded))` — start `u32::MAX + 1` wraps to `0`, producing `slice(0..)` instead of an empty/invalid range.\n\n`Vec::slice`:\n- `Vec::slice(0..=u32::MAX)` — same as `Bytes`, end wraps to `0`, returning empty.\n- `Vec::slice((Bound::Excluded(u32::MAX), Bound::Unbounded))` — same as `Bytes`, start wraps to `0`.\n\n`Prng::gen_range`:\n- `Prng::gen_range((Bound::Unbounded, Bound::Excluded(0)))` — end `0 - 1` wraps to `u64::MAX`, producing range `0..=u64::MAX` instead of an empty/invalid range.\n- `Prng::gen_range((Bound::Excluded(u64::MAX), Bound::Unbounded))` — start `u64::MAX + 1` wraps to `0`, producing range `0..=u64::MAX` instead of an empty/invalid range.\n\nNote that some cases where the overflow was permitted and wrapped on the guest side are caught by the Soroban Env Host and cause a trap host side with error `HostError: Error(Object, IndexBounds)` `object index out of bounds`, because the wrapped values create invalid inputs:\n- `Bytes::slice(u32::MAX..=u32::MAX)` — both start `u32::MAX + 1` and end `u32::MAX + 1` wrap to `0`, producing `slice(0..0)`.\n- `Vec::slice(u32::MAX..=u32::MAX)` — same as `Bytes`, both wrap to `0`.\n\n\n### Patches\n\nThe fix replaces bare arithmetic with `checked_add` / `checked_sub`, ensuring overflow traps regardless of the `overflow-checks` profile setting.\n\n### Workarounds\n\nContract workspaces can be configured with the following profile to enable overflow checks on the arithmetic operations. This is the best practice when developing Soroban contracts, and the default if using the contract boilerplate generated using `stellar contract init`:\n\n```toml\n[profile.release]\noverflow-checks = true\n```\n\nAlternatively, contracts can validate range bounds before passing them to `slice` or `gen_range` to ensure the conversions cannot overflow:\n\n- Do not pass `Bound::Excluded(u32::MAX)` or `Bound::Included(u32::MAX)` to `Bytes::slice` or `Vec::slice`.\n- Do not pass `Bound::Excluded(u64::MAX)` as a start bound or `Bound::Excluded(0)` as an end bound to `Prng::gen_range::<u64>`.\n\n### References\n\n- https://github.com/stellar/rs-soroban-sdk/pull/1703\n- https://github.com/stellar/rs-soroban-sdk/releases/tag/v25.0.2\n- https://github.com/stellar/rs-soroban-sdk/releases/tag/v23.5.1\n- https://github.com/stellar/rs-soroban-sdk/releases/tag/v22.0.9",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "soroban-sdk"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "25.0.0"
      }, {
        "fixed" : "25.0.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "soroban-sdk"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "23.0.0"
      }, {
        "fixed" : "23.5.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "soroban-sdk"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "22.0.9"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/stellar/rs-soroban-sdk/security/advisories/GHSA-96xm-fv9w-pf3f"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-24889"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/stellar/rs-soroban-sdk/pull/1703"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/stellar/rs-soroban-sdk/commit/3890521426d71bb4d892b21f5a283a1e836cfa38"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/stellar/rs-soroban-sdk/commit/59fcef437260ed4da42d1efb357137a5c166c02e"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/stellar/rs-soroban-sdk/commit/c2757c6d774dbb28b34a0b77ffe282e59f0f8462"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/stellar/rs-soroban-sdk"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/stellar/rs-soroban-sdk/releases/tag/v22.0.9"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/stellar/rs-soroban-sdk/releases/tag/v23.5.1"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/stellar/rs-soroban-sdk/releases/tag/v25.0.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-190" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-01-28T22:20:35Z",
    "nvd_published_at" : "2026-01-28T22:15:56Z"
  }
}