CVE-2026-24889

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 72% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

soroban-sdk is a Rust SDK for Soroban contracts. Arithmetic overflow can be triggered in the Bytes::slice, Vec::slice, and Prng::gen_range (for u64) methods in the soroban-sdk in versions up to and including 25.0.1, 23.5.1, and 25.0.2. 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. The fix available in 25.0.1, 23.5.1, and 25.0.2 replaces bare arithmetic with checked_add / checked_sub, ensuring overflow traps regardless of the overflow-checks profile setting. As a workaround, contract workspaces can be configured with a profile available in the GitHub Securtity Advisory 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. Alternatively, contracts can validate range bounds before passing them to slice or gen_range to ensure the conversions cannot overflow.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

January 28, 2026

Last Modified

June 17, 2026

Advisory Details (8)

Auto-updated Aug 9, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Overflow in Bytes::slice, Vec::slice, GenRange::gen_range for u64 · Advisory · stellar/rs-soroban-sdk · GitHub

https://github.com/stellar/rs-soroban-sdk/security/advisories/GHSA-96xm-fv9w-pf3f
github_release Patch Available

25.0.2

Patch available: stellar/rs-soroban-sdk v25.0.2

https://github.com/stellar/rs-soroban-sdk/releases/tag/v25.0.2
github_release Patch Available

23.5.1

Patch available: stellar/rs-soroban-sdk v23.5.1

https://github.com/stellar/rs-soroban-sdk/releases/tag/v23.5.1
github_release Patch Available

22.0.9

Patch available: stellar/rs-soroban-sdk v22.0.9

https://github.com/stellar/rs-soroban-sdk/releases/tag/v22.0.9
github_pr Patch Available

Fix range bound overflow in Vec/Bytes slice and GenRange gen_range for u64

Patch available: stellar/rs-soroban-sdk v25.0.2 (PR #1703 merged 2026-01-28)

https://github.com/stellar/rs-soroban-sdk/pull/1703
github_commit Patch Available

commit c2757c6d774d (stellar/rs-soroban-sdk)

Patch available: stellar/rs-soroban-sdk v25.0.2 (contains commit c2757c6d774d)

https://github.com/stellar/rs-soroban-sdk/commit/c2757c6d774dbb28b34a0b77ffe282e59f0f8462
github_commit Patch Available

commit 59fcef437260 (stellar/rs-soroban-sdk)

Patch available: stellar/rs-soroban-sdk v23.5.1 (contains commit 59fcef437260)

https://github.com/stellar/rs-soroban-sdk/commit/59fcef437260ed4da42d1efb357137a5c166c02e
github_commit Patch Available

commit 3890521426d7 (stellar/rs-soroban-sdk)

Patch available: stellar/rs-soroban-sdk v22.0.9 (contains commit 3890521426d7)

https://github.com/stellar/rs-soroban-sdk/commit/3890521426d71bb4d892b21f5a283a1e836cfa38

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
soroban-sdk22.0.9

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 159 total refreshes for this CVE.

  1. 2026-09-19 00:06 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-31 04:03 UTCOSV refresh
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:48 UTCEPSS rescore
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
Show 75 more
  1. 2026-08-19 17:03 UTCEPSS rescore
  2. 2026-08-18 13:48 UTCEPSS rescore
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 11:58 UTCEG score recompute
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 04:03 UTCEG score recompute
  10. 2026-08-12 13:50 UTCEPSS rescore
  11. 2026-08-11 13:42 UTCEPSS rescore
  12. 2026-08-11 00:00 UTCEPSS rescore
  13. 2026-08-09 16:35 UTCEG score recompute
  14. 2026-08-09 13:46 UTCEPSS rescore
  15. 2026-08-08 16:37 UTCEPSS rescore
  16. 2026-08-07 23:15 UTCEG score recompute
  17. 2026-08-06 13:46 UTCEPSS rescore
  18. 2026-08-06 04:45 UTCEG score recompute
  19. 2026-08-05 19:17 UTCEPSS rescore
  20. 2026-08-04 15:10 UTCEPSS rescore
  21. 2026-08-03 10:36 UTCEPSS rescore
  22. 2026-08-02 21:55 UTCEG score recompute
  23. 2026-08-02 02:26 UTCEPSS rescore
  24. 2026-08-01 04:16 UTCEPSS rescore
  25. 2026-07-31 04:46 UTCOSV refresh
  26. 2026-07-30 16:27 UTCEPSS rescore
  27. 2026-07-30 01:30 UTCEPSS rescore
  28. 2026-07-27 14:13 UTCEPSS rescore
  29. 2026-07-26 14:54 UTCEPSS rescore
  30. 2026-07-26 14:54 UTCEPSS rescore
  31. 2026-07-25 14:17 UTCEPSS rescore
  32. 2026-07-25 14:17 UTCEPSS rescore
  33. 2026-07-24 14:17 UTCEPSS rescore
  34. 2026-07-23 14:18 UTCEPSS rescore
  35. 2026-07-23 14:18 UTCEPSS rescore
  36. 2026-07-23 03:07 UTCEG score recompute
  37. 2026-07-22 14:08 UTCEPSS rescore
  38. 2026-07-21 15:24 UTCEPSS rescore
  39. 2026-07-21 15:24 UTCEPSS rescore
  40. 2026-07-20 17:08 UTCEPSS rescore
  41. 2026-07-19 14:31 UTCEPSS rescore
  42. 2026-07-19 14:31 UTCEPSS rescore
  43. 2026-07-19 02:29 UTCEPSS rescore
  44. 2026-07-19 02:28 UTCEPSS rescore
  45. 2026-07-18 10:04 UTCEPSS rescore
  46. 2026-07-18 10:04 UTCEPSS rescore
  47. 2026-07-16 17:03 UTCEPSS rescore
  48. 2026-07-16 17:03 UTCEPSS rescore
  49. 2026-07-15 16:57 UTCEPSS rescore
  50. 2026-07-15 16:57 UTCEPSS rescore
  51. 2026-07-15 02:00 UTCEPSS rescore
  52. 2026-07-15 02:00 UTCEPSS rescore
  53. 2026-07-13 22:30 UTCEPSS rescore
  54. 2026-07-13 12:38 UTCOSV refresh
  55. 2026-07-13 06:13 UTCEPSS rescore
  56. 2026-07-13 06:13 UTCEPSS rescore
  57. 2026-07-12 05:46 UTCEPSS rescore
  58. 2026-07-12 05:46 UTCEPSS rescore
  59. 2026-07-11 08:27 UTCEPSS rescore
  60. 2026-07-09 19:10 UTCEPSS rescore
  61. 2026-07-08 15:15 UTCEPSS rescore
  62. 2026-07-08 15:15 UTCEPSS rescore
  63. 2026-07-07 13:46 UTCEPSS rescore
  64. 2026-07-06 16:27 UTCEPSS rescore
  65. 2026-07-06 16:27 UTCEPSS rescore
  66. 2026-07-06 02:23 UTCEPSS rescore
  67. 2026-07-06 02:23 UTCEPSS rescore
  68. 2026-07-05 02:30 UTCEPSS rescore
  69. 2026-07-04 06:31 UTCEPSS rescore
  70. 2026-07-04 06:31 UTCEPSS rescore
  71. 2026-07-01 15:06 UTCEPSS rescore
  72. 2026-07-01 15:06 UTCEPSS rescore
  73. 2026-06-30 23:22 UTCEPSS rescore
  74. 2026-06-30 23:22 UTCEPSS rescore
  75. 2026-06-29 14:06 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-24889?
CVE-2026-24889 is a medium vulnerability published on January 28, 2026. soroban-sdk is a Rust SDK for Soroban contracts. Arithmetic overflow can be triggered in the Bytes::slice, Vec::slice, and Prng::genrange (for u64) methods in the soroban-sdk in versions up to and including 25.0.1, 23.5.1, and 25.0.2. Contracts that pass user-controlled or computed range bounds to…
When was CVE-2026-24889 disclosed?
CVE-2026-24889 was first published in the National Vulnerability Database on January 28, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-24889 actively exploited?
CVE-2026-24889 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.4% of all scored CVEs.
What is the CVSS score of CVE-2026-24889?
CVE-2026-24889 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-24889?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24889, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-24889

Explore →

Is Your Infrastructure Affected by CVE-2026-24889?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.