NVD / CVE Program· CNA GitHub_M

CVE-2026-32322: soroban-sdk: `Fr` scalar field equality comparison bypasses modular reduction

Noroxi assessment

Priority: Monitor (action score 21/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: stellar rs-soroban-sdk 22.0.11.

Low priority for now. Upgrade to stellar rs-soroban-sdk 22.0.11 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

soroban-sdk is a Rust SDK for Soroban contracts. Prior to 22.0.11, 23.5.3, and 25.3.0, The Fr (scalar field) types for BN254 and BLS12-381 in soroban-sdk compared values using their raw U256 representation without first reducing modulo the field modulus r. This caused mathematically equal field elements to compare as not-equal when one or both values were unreduced (i.e., >= r). The vulnerability requires an attacker to supply crafted Fr values through contract inputs, and compare them directly without going through host-side arithmetic operations. Smart contracts that rely on Fr equality checks for security-critical logic could produce incorrect results. The impact depends on how the affected contract uses Fr equality comparisons, but can result in incorrect authorization decisions or validation bypasses in contracts that perform equality checks on user-supplied scalar values. This vulnerability is fixed in 22.0.11, 23.5.3, and 25.3.0.

MediumCVSS 5.3 · v3.1—No exploit Fix available

Pre-auth

GHSA-x2hw-px52-wp4m

Published: Mar 13, 2026
Updated: Jun 17, 2026
EPSS: 0.2% · 21th percentile
CWE: CWE-697

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 21 / 40 · 5.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 5.3; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
stellar	rs-soroban-sdk	cpe:2.3:a:stellar:rs-soroban-sdk

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

stellar rs-soroban-sdkbefore 22.0.11
stellar rs-soroban-sdk23.0.0 and later · before 23.5.3
stellar rs-soroban-sdk25.0.0 and later · before 25.3.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

stellar rs-soroban-sdk
- >= 25.0.0, < 25.3.0, >= 23.0.0, < 23.5.3, < 22.0.11affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
crates.io	soroban-sdk	from 23.0.0 · before 23.5.3	23.5.3
crates.io	soroban-sdk	from 25.0.0 · before 25.3.0	25.3.0
crates.io	soroban-sdk	before 22.0.11	22.0.11

Same product

stellar: all records

Other highest-scoring records for the same primary product.

CVE-2026-26267rs-soroban-sdk #[contractimpl] macro calls inherent function instead of trait function when names collide
30Monitor
CVE-2026-24889soroban-sdk has overflow in Bytes::slice, Vec::slice, GenRange::gen_range for u64
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
stellar rs-soroban-sdk	22.0.11 · description	Vendor (CNA)
crates.io:soroban-sdk	22.0.11	Package registry (OSV)
crates.io:soroban-sdk	23.5.3	Package registry (OSV)
crates.io:soroban-sdk	25.3.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope