CVE-2026-32322: CWE-697: Incorrect Comparison in stellar rs-soroban-sdk
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.
AI Analysis
Technical Summary
The vulnerability CVE-2026-32322 affects the stellar rs-soroban-sdk, a Rust software development kit used for building Soroban smart contracts on the Stellar blockchain platform. The issue lies in the implementation of equality comparisons for Fr scalar field types associated with BN254 and BLS12-381 elliptic curves. These Fr values represent elements in a finite field used in cryptographic operations. The flawed comparison logic directly compares the raw 256-bit unsigned integer (U256) representations of these values without first reducing them modulo the field modulus r. Since field elements can have multiple integer representations that are congruent modulo r, failing to reduce before comparison means that two mathematically equal elements may be considered unequal if one or both are unreduced (i.e., greater than or equal to r). This incorrect comparison can cause smart contracts that rely on Fr equality checks for security-critical decisions—such as authorization or validation—to behave incorrectly. An attacker can exploit this by supplying specially crafted Fr values as inputs to the contract, triggering erroneous logic paths that may bypass intended security checks. The vulnerability requires no authentication or user interaction beyond supplying inputs to the contract. It affects multiple versions of the rs-soroban-sdk prior to 22.0.11, 23.5.3, and 25.3.0, where the issue has been fixed. The CVSS 3.1 base score is 5.3, reflecting a medium severity with network attack vector, low complexity, no privileges required, and no user interaction. There are no known exploits reported in the wild as of the publication date.
Potential 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.
Mitigation Recommendations
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.
Affected Countries
United States, Germany, Japan, South Korea, Singapore, Switzerland, United Kingdom, Canada, Australia, Netherlands
CVE-2026-32322: CWE-697: Incorrect Comparison in stellar rs-soroban-sdk
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-32322 affects the stellar rs-soroban-sdk, a Rust software development kit used for building Soroban smart contracts on the Stellar blockchain platform. The issue lies in the implementation of equality comparisons for Fr scalar field types associated with BN254 and BLS12-381 elliptic curves. These Fr values represent elements in a finite field used in cryptographic operations. The flawed comparison logic directly compares the raw 256-bit unsigned integer (U256) representations of these values without first reducing them modulo the field modulus r. Since field elements can have multiple integer representations that are congruent modulo r, failing to reduce before comparison means that two mathematically equal elements may be considered unequal if one or both are unreduced (i.e., greater than or equal to r). This incorrect comparison can cause smart contracts that rely on Fr equality checks for security-critical decisions—such as authorization or validation—to behave incorrectly. An attacker can exploit this by supplying specially crafted Fr values as inputs to the contract, triggering erroneous logic paths that may bypass intended security checks. The vulnerability requires no authentication or user interaction beyond supplying inputs to the contract. It affects multiple versions of the rs-soroban-sdk prior to 22.0.11, 23.5.3, and 25.3.0, where the issue has been fixed. The CVSS 3.1 base score is 5.3, reflecting a medium severity with network attack vector, low complexity, no privileges required, and no user interaction. There are no known exploits reported in the wild as of the publication date.
Potential 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.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-03-11T21:16:21.661Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69b3375b2f860ef943024593
Added to database: 3/12/2026, 9:59:55 PM
Last enriched: 3/20/2026, 2:37:57 AM
Last updated: 4/27/2026, 3:25:57 AM
Views: 111
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.