{ "document": { "category": "csaf_base", "csaf_version": "2.0", "distribution": { "tlp": { "label": "WHITE" } }, "lang": "en", "notes": [ { "category": "legal_disclaimer", "text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings." } ], "publisher": { "category": "coordinator", "contact_details": "cert@ncsc.nl", "name": "National Cyber Security Centre", "namespace": "https://www.ncsc.nl/" }, "title": "CVE-2026-32322", "tracking": { "current_release_date": "2026-03-23T04:15:41.011564Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-32322", "initial_release_date": "2026-03-12T22:39:02.036266Z", "revision_history": [ { "date": "2026-03-12T22:39:02.036266Z", "number": "1", "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (3).| References created (1).| CWES updated (1)." }, { "date": "2026-03-12T22:39:11.056098Z", "number": "2", "summary": "NCSC Score created." }, { "date": "2026-03-13T07:35:33.427035Z", "number": "3", "summary": "NCSC Score updated." }, { "date": "2026-03-13T14:13:29.983035Z", "number": "4", "summary": "Source created.| CVE status created. (valid)| EPSS created." }, { "date": "2026-03-13T15:38:47.623226Z", "number": "5", "summary": "Unknown change." }, { "date": "2026-03-13T20:32:18.477710Z", "number": "6", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (1).| CWES updated (1)." }, { "date": "2026-03-13T20:32:26.680505Z", "number": "7", "summary": "NCSC Score updated." }, { "date": "2026-03-13T21:12:46.455874Z", "number": "8", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (7).| CWES updated (1)." }, { "date": "2026-03-16T17:45:19.769541Z", "number": "9", "summary": "References created (1)." }, { "date": "2026-03-16T17:45:31.887587Z", "number": "10", "summary": "NCSC Score updated." }, { "date": "2026-03-19T15:28:44.516564Z", "number": "11", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (8).| CWES updated (1)." }, { "date": "2026-03-19T20:31:05.669617Z", "number": "12", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products connected (3).| Product Identifiers created (3).| References created (1).| CWES updated (1)." }, { "date": "2026-03-19T20:31:14.086367Z", "number": "13", "summary": "NCSC Score updated." }, { "date": "2026-03-20T09:31:04.666100Z", "number": "14", "summary": "Source connected.| CVE status created. (valid)| EPSS created." }, { "date": "2026-03-20T09:31:08.720948Z", "number": "15", "summary": "NCSC Score updated." } ], "status": "interim", "version": "15" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/<22.0.11", "product": { "name": "vers:unknown/<22.0.11", "product_id": "CSAFPID-5811019", "product_identification_helper": { "cpe": "cpe:2.3:a:stellar:rs-soroban-sdk:*:*:*:*:*:rust:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/>=23.0.0|<23.5.3", "product": { "name": "vers:unknown/>=23.0.0|<23.5.3", "product_id": "CSAFPID-5811018", "product_identification_helper": { "cpe": "cpe:2.3:a:stellar:rs-soroban-sdk:*:*:*:*:*:rust:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/>=25.0.0|<25.3.0", "product": { "name": "vers:unknown/>=25.0.0|<25.3.0", "product_id": "CSAFPID-5811017", "product_identification_helper": { "cpe": "cpe:2.3:a:stellar:rs-soroban-sdk:*:*:*:*:*:rust:*:*" } } } ], "category": "product_name", "name": "rs-soroban-sdk" } ], "category": "vendor", "name": "stellar" } ] }, "vulnerabilities": [ { "cve": "CVE-2026-32322", "notes": [ { "category": "description", "text": "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.", "title": "cveprojectv5 - https://www.cve.org/CVERecord?id=CVE-2026-32322" }, { "category": "description", "text": "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.", "title": "nvd - https://nvd.nist.gov/vuln/detail/CVE-2026-32322" }, { "category": "description", "text": "# Security Advisory: Incorrect Equality for Fr Scalar Field Types (BN254, BLS12-381)\n\n## Summary\n\nMissing modular reduction in `Fr` causes incorrect equality comparisons for BN254 and BLS12-381 types in soroban-sdk.\n\n## Impact\n\nThe `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`). \n\nThe vulnerability requires an attacker to supply crafted `Fr` values through contract inputs, and compare them directly without going through host-side arithmetic operations.\n\nSmart 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.\n\n## Details\n\n`Fr` types for both curves are wrappers around `U256`. The `PartialEq` implementation compared the raw `U256` values directly. However, the constructors (`from_u256`, `from_bytes`, `From`) accepted arbitrary `U256` values without reducing them modulo `r`. This meant two `Fr` values representing the same field element (e.g., `1` and `r + 1`) could have different internal representations and compare as not-equal.\n\nThis issue was compounded by an asymmetry: all host-side arithmetic operations (`fr_add`, `fr_sub`, `fr_mul`, `fr_pow`, `fr_inv`) always return canonically reduced results in `[0, r)`, while user-constructed `Fr` values could hold unreduced representations. Comparing a user-supplied `Fr` against a host-computed `Fr` would therefore produce incorrect results even when the underlying field elements were identical.\n\n### Example\n\n```rust\nlet r = /* BN254 scalar field modulus */;\nlet a = Fr::from_u256(r + 1); // unreduced, stores r+1\nlet b = Fr::from_u256(1); // reduced, stores 1\n\n// a and b represent the same field element (1), but compared as NOT equal\nassert_eq!(a, b); // FAILED before the fix\n```\n\n## Patches\n\nAll `Fr` construction paths now reduce the input modulo `r`, ensuring a canonical representation in `[0, r)`. This guarantees that equal field elements always have identical internal representations, making the existing `PartialEq` comparison correct.\n\nAdditionally, `Fp` and `Fp2` base field types for both curves now validate that values are strictly less than the field modulus on construction, rejecting out-of-range inputs.\n\n## Workarounds\n\nIf upgrading is not immediately possible:\n- Manually reduce the underlying `U256` via `rem_euclid` by the field modulus `r` before constructing `Fr`, or round-trip through host `Fr` arithmetic (e.g., `fr_add(val, zero)`) which always returns reduced results. Note: BN254 does not expose dedicated `Fr` host functions, so `rem_euclid` is the only option there.\n\n## Recommendations\n\n- Upgrade to the patched version of `soroban-sdk`.\n- Review any deployed contracts that accept `Fr` values as input, and compare those values using `==`, `!=`, or `assert_eq!`. These contracts may be vulnerable if an attacker can supply unreduced scalar values to bypass equality checks.", "title": "github - https://github.com/advisories/GHSA-x2hw-px52-wp4m" }, { "category": "description", "text": "# Security Advisory: Incorrect Equality for Fr Scalar Field Types (BN254, BLS12-381)\n\n## Summary\n\nMissing modular reduction in `Fr` causes incorrect equality comparisons for BN254 and BLS12-381 types in soroban-sdk.\n\n## Impact\n\nThe `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`). \n\nThe vulnerability requires an attacker to supply crafted `Fr` values through contract inputs, and compare them directly without going through host-side arithmetic operations.\n\nSmart 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.\n\n## Details\n\n`Fr` types for both curves are wrappers around `U256`. The `PartialEq` implementation compared the raw `U256` values directly. However, the constructors (`from_u256`, `from_bytes`, `From`) accepted arbitrary `U256` values without reducing them modulo `r`. This meant two `Fr` values representing the same field element (e.g., `1` and `r + 1`) could have different internal representations and compare as not-equal.\n\nThis issue was compounded by an asymmetry: all host-side arithmetic operations (`fr_add`, `fr_sub`, `fr_mul`, `fr_pow`, `fr_inv`) always return canonically reduced results in `[0, r)`, while user-constructed `Fr` values could hold unreduced representations. Comparing a user-supplied `Fr` against a host-computed `Fr` would therefore produce incorrect results even when the underlying field elements were identical.\n\n### Example\n\n```rust\nlet r = /* BN254 scalar field modulus */;\nlet a = Fr::from_u256(r + 1); // unreduced, stores r+1\nlet b = Fr::from_u256(1); // reduced, stores 1\n\n// a and b represent the same field element (1), but compared as NOT equal\nassert_eq!(a, b); // FAILED before the fix\n```\n\n## Patches\n\nAll `Fr` construction paths now reduce the input modulo `r`, ensuring a canonical representation in `[0, r)`. This guarantees that equal field elements always have identical internal representations, making the existing `PartialEq` comparison correct.\n\nAdditionally, `Fp` and `Fp2` base field types for both curves now validate that values are strictly less than the field modulus on construction, rejecting out-of-range inputs.\n\n## Workarounds\n\nIf upgrading is not immediately possible:\n- Manually reduce the underlying `U256` via `rem_euclid` by the field modulus `r` before constructing `Fr`, or round-trip through host `Fr` arithmetic (e.g., `fr_add(val, zero)`) which always returns reduced results. Note: BN254 does not expose dedicated `Fr` host functions, so `rem_euclid` is the only option there.\n\n## Recommendations\n\n- Upgrade to the patched version of `soroban-sdk`.\n- Review any deployed contracts that accept `Fr` values as input, and compare those values using `==`, `!=`, or `assert_eq!`. These contracts may be vulnerable if an attacker can supply unreduced scalar values to bypass equality checks.", "title": "github - https://api.github.com/advisories/GHSA-x2hw-px52-wp4m" }, { "category": "description", "text": "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.", "title": "nvd - https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-32322" }, { "category": "other", "text": "0.00038", "title": "EPSS" }, { "category": "other", "text": "4.7", "title": "NCSC Score" } ], "product_status": { "known_affected": [ "CSAFPID-5811017", "CSAFPID-5811018", "CSAFPID-5811019" ] }, "references": [ { "category": "external", "summary": "Source - cveprojectv5", "url": "https://www.cve.org/CVERecord?id=CVE-2026-32322" }, { "category": "external", "summary": "Source raw - cveprojectv5", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/32xxx/CVE-2026-32322.json" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-32322" }, { "category": "external", "summary": "Source raw - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Source - nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32322" }, { "category": "external", "summary": "Source raw - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-32322" }, { "category": "external", "summary": "Source - github", "url": "https://github.com/advisories/GHSA-x2hw-px52-wp4m" }, { "category": "external", "summary": "Source raw - github", "url": "https://api.github.com/advisories/GHSA-x2hw-px52-wp4m" }, { "category": "external", "summary": "Source - github", "url": "https://api.github.com/advisories/GHSA-x2hw-px52-wp4m" }, { "category": "external", "summary": "Source - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-32322" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd", "url": "https://github.com/stellar/rs-soroban-sdk/security/advisories/GHSA-x2hw-px52-wp4m" }, { "category": "external", "summary": "Reference - github", "url": "https://github.com/stellar/rs-soroban-sdk/pull/1750" }, { "category": "external", "summary": "Reference - github", "url": "https://github.com/stellar/rs-soroban-sdk/commit/082424b30bf22ea7fb8c79f16ccd135e0ae9f3db" }, { "category": "external", "summary": "Reference - github", "url": "https://github.com/stellar/rs-soroban-sdk/releases/tag/v22.0.11" }, { "category": "external", "summary": "Reference - github", "url": "https://github.com/stellar/rs-soroban-sdk/releases/tag/v23.5.3" }, { "category": "external", "summary": "Reference - github", "url": "https://github.com/stellar/rs-soroban-sdk/releases/tag/v25.3.0" }, { "category": "external", "summary": "Reference - github", "url": "https://github.com/advisories/GHSA-x2hw-px52-wp4m" }, { "category": "external", "summary": "Reference - github", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32322" } ], "scores": [ { "cvss_v3": { "version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N", "baseScore": 5.3, "baseSeverity": "MEDIUM" }, "products": [ "CSAFPID-5811017", "CSAFPID-5811018", "CSAFPID-5811019" ] } ], "title": "CVE-2026-32322" } ] }