VulnerabilityPublished 12 Mar 2026

CVE-2026-32322: stellar rs-soroban-sdk · Incorrect Comparison

Affects stellar rs-soroban-sdkSource CVE Database V5

Compare

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

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 25.3.0, 23.5.3, 22.0.11

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 12 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.

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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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.3.0, 23.5.3 or 22.0.11; github/stellar/rs-soroban-sdk to 22.0.11.

Affected software

Product	Affected	Fixed in
stellarrs-soroban-sdk	Affected >=25.0.0 <25.3.0	Fixed in 25.3.0
stellarrs-soroban-sdk	Affected >=23.0.0 <23.5.3	Fixed in 23.5.3
stellarrs-soroban-sdk	Affected <22.0.11	Fixed in 22.0.11
crates.iogithub/stellar/rs-soroban-sdk`pkg:cargo/github/stellar/rs-soroban-sdk`Other threats	Affected <22.0.11	Fixed in 22.0.11

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

AI-suggested

To mitigate this vulnerability, organizations and developers should immediately upgrade to the fixed versions of the rs-soroban-sdk: 22.0.11, 23.5.3, or 25.3.0 or later. Auditing existing smart contracts for reliance on Fr equality comparisons is critical; contracts performing direct equality checks on user-supplied scalar values should be reviewed and potentially refactored to use host-side arithmetic operations that ensure modular reduction before comparison. Developers should implement additional validation layers to verify that all Fr values are reduced modulo r before any equality checks. Incorporating comprehensive unit and integration tests that cover edge cases involving unreduced Fr values can help detect similar logic flaws. Monitoring blockchain transactions for anomalous contract behavior or unexpected authorization bypasses may provide early warning of exploitation attempts. Finally, educating developers on the correct handling of finite field elements and cryptographic primitives in Soroban contracts will reduce the risk of similar vulnerabilities.

Description

CVE-2026-32322 is a medium severity vulnerability in the stellar rs-soroban-sdk, a Rust SDK for Soroban smart contracts. The flaw arises from incorrect equality comparisons of Fr (scalar field) types for BN254 and BLS12-381 curves, where values are compared using their raw U256 representation without modular reduction. This causes mathematically equal field elements to be treated as unequal if unreduced, potentially leading to incorrect authorization or validation bypasses in smart contracts relying on these checks. Exploitation requires an attacker to supply crafted Fr values as contract inputs and depends on the contract performing direct equality checks on these values. The vulnerability affects versions prior to 22.0.11, 23.5.3, and 25.3.

Impact

The impact of this vulnerability depends heavily on how smart contracts utilize Fr equality comparisons. Contracts that rely on these comparisons for critical security functions—such as verifying user authorization, validating transaction parameters, or enforcing business logic—may produce incorrect results. This can lead to unauthorized access, bypass of validation checks, or other logic flaws that compromise contract integrity. Since Soroban contracts are deployed on the Stellar blockchain, exploitation could undermine trust in decentralized applications built on this platform. The vulnerability does not directly affect confidentiality or availability but impacts integrity by allowing incorrect decisions. Given the increasing adoption of Soroban for decentralized finance (DeFi) and other blockchain applications, the risk extends to financial services, asset management, and identity verification systems using affected versions of the SDK. Organizations running Soroban contracts on vulnerable SDK versions face potential financial loss, reputational damage, and regulatory scrutiny if exploited.

CWE-697Incorrect Comparison (opens in a new tab)
Pillar weakness
The product compares two entities in a security-relevant context, but the comparison is incorrect.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Attack patterns
Buffer Overflow via Environment Variables (opens in a new tab)
Double Encoding (opens in a new tab)
Client-side Injection-induced Buffer Overflow (opens in a new tab)
Command Delimiters (opens in a new tab)
Flash Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/stellar/rs-soroban-sdk/security/advisories/GHSA-x2hw-px52-wp4m (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 20 Mar 2026, 02:37 UTC

WeaknessesCWE-697

Technical details

References

Community reviews

Related threats