CVE-2026-24889VulnerabilityPublished 28 Jan 2026

CVE-2026-24889: stellar rs-soroban-sdk · Integer Overflow or Wraparound

Affects stellar rs-soroban-sdkSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 25.0.2 : update stellar rs-soroban-sdk when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 25.0.2, 23.5.1, 22.0.9 +1

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade rs-soroban-sdk to 25.0.2, 23.5.1 or 22.0.9; github/stellar/rs-soroban-sdk to 25.0.2, 23.5.2 or 22.0.9.

Affected software

Product	Affected	Fixed in
stellarrs-soroban-sdk	Affected <22.0.9 >=23.0.0 <23.5.1 >=25.0.0 <25.0.2	Fixed in 25.0.2 23.5.1 22.0.9
crates.iogithub/stellar/rs-soroban-sdk`pkg:cargo/github/stellar/rs-soroban-sdk`Other threats	Affected <22.0.9 >=23.0.0 <23.5.2 >=25.0.0 <25.0.2	Fixed in 22.0.9 23.5.2 25.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately verify the versions of rs-soroban-sdk in use and upgrade to patched versions 22.0.9 or later, 23.5.1 or later, and 25.0.2 or later as applicable. It is critical to ensure that the Rust compiler's overflow-checks feature is enabled (overflow-checks = true) in all build profiles, including release builds, to prevent silent wraparounds. Developers should audit Soroban contracts to confirm that user inputs or computed range bounds passed to Bytes::slice, Vec::slice, and Prng::gen_range are validated rigorously to prevent out-of-bound or overflow conditions. Employing checked arithmetic methods (checked_add, checked_sub) explicitly in contract code can provide additional safety. Organizations should integrate static analysis and fuzz testing focused on boundary conditions in contract development pipelines. Monitoring contract behavior post-deployment for anomalies in state or random number generation can help detect exploitation attempts. Finally, educating developers on this vulnerability and enforcing secure coding standards for Soroban contracts will reduce future risks.

Description

CVE-2026-24889 is an integer overflow vulnerability in the Stellar rs-soroban-sdk Rust SDK used for Soroban smart contracts. The flaw occurs in the Bytes::slice, Vec::slice, and Prng::gen_range methods when user-controlled or computed range bounds cause arithmetic overflow or wraparound, potentially corrupting contract state or generating unintended random numbers. This vulnerability affects versions prior to 22.0.9, between 23.0.0 and 23.5.1, and between 25.0.

Impact

For European organizations leveraging the Stellar blockchain and Soroban smart contracts, this vulnerability could lead to subtle and hard-to-detect corruption of contract state. This may cause financial discrepancies, erroneous contract executions, or unintended behavior in decentralized applications, especially those handling sensitive transactions or assets. Since the vulnerability does not affect confidentiality or availability directly, the primary risk is integrity loss, which can undermine trust in blockchain-based services. Organizations in fintech, decentralized finance (DeFi), and blockchain development sectors are particularly at risk if they use vulnerable SDK versions without overflow checks enabled. The silent nature of the overflow means that corrupted states could propagate unnoticed, complicating incident response and recovery. Additionally, the generation of random numbers from unintended ranges could weaken cryptographic or probabilistic contract logic, further increasing risk. Given the medium severity, the impact is significant but not catastrophic, provided that best practices are followed. However, failure to address this vulnerability could lead to financial loss, reputational damage, and regulatory scrutiny under European data and financial regulations.

CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
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.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Feb 2026, 08:55 UTC

WeaknessesCWE-190

Technical details

References

Community reviews

Related threats