NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀
🦀 crates.io
Not in CISA KEV
HIGH severity

soroban-fixed-point-math has Incorrect Rounding and Overflow Handling in Signed Fixed-Point Math with NegativesGHSA-x5m4-43jf-hh65

HIGHFix: script3/soroban-fixed-point-math@c9233f7

GHSA-x5m4-43jf-hh65 is a high-severity (CVSS 7.5) CWE-682 vulnerability in soroban-fixed-point-math. A fix is available for soroban-fixed-point-math — see the affected versions and patch details below.

Also known asCVE-2026-24783
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-x5m4-43jf-hh65.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk-0.00%
Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk
0.00%0.30%0.61%0.91%0.0%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🦀soroban-fixed-point-math🦀soroban-fixed-point-math

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Incorrect rounding direction for signed mul and div operations

The mulDiv(x, y, z) function incorrectly handled cases where both the intermediate product $x * y$ and the divisor $z$ were negative. The logic assumed that if the intermediate product was negative, the final result must also be negative, neglecting the sign of $z$.

This resulted in rounding being applied in the wrong direction for cases where both $x * y$ and $z$ were negative. The functions most at risk are fixed_div_floor and fixed_div_ceil, as they often use non-constant numbers as the divisor $z$ in mulDiv.

This error is present in all signed FixedPoint and SorobanFixedPoint implementations, including i64, i128, and I256.

Negative Overflow in i64

The mulDiv(x, y, z) function for i64 used the i128 type to handle "phantom overflows". These are overflows that occur intermediately during a calculation, like when computing the intermediate product $x * y$. When the final result of mulDiv was computed in i128, it was scaled back down to i64 before returning. While the code verified that the result did not exceed i64::MAX, it did not check against i64::MIN.

This caused negative results smaller than i64:MIN to wrap around to a large positive number instead of being caught as an overflow.

This error only exists for the FixedPoint implementation of i64.

Patches

  • v1.3.0 users should upgrade to patch v1.3.1
  • v1.4.0 users should upgrade to patch v1.4.1

All versions >=v1.4.1 contain the patch.

Workarounds

There are no known workarounds. Upgrade to the patched version.

Credits

soroban-fixed-point-math would like to thank the team at Certora for discovering and reporting the issue.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iosoroban-fixed-point-math≥ 1.4.0&&< 1.4.11.4.1cargo update -p soroban-fixed-point-math --precise 1.4.1
🦀crates.iosoroban-fixed-point-math≥ 1.3.0&&< 1.3.11.3.1cargo update -p soroban-fixed-point-math --precise 1.3.1

Affected Products

1 product · 2 configurations
Application
soroban-fixed-point-mathscript3
2 versions
1.3.01.4.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for soroban-fixed-point-math, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update soroban-fixed-point-math to 1.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x5m4-43jf-hh65 is resolved across your whole dependency graph.

  3. Workarounds

    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

### Impact #### Incorrect rounding direction for signed mul and div operations The `mulDiv(x, y, z)` function incorrectly handled cases where both the intermediate product $x * y$ and the divisor $z$ were negative. The logic assumed that if the intermediate product was negative, the final result must also be negative, neglecting the sign of $z$. This resulted in rounding being applied in the wrong direction for cases where both $x * y$ and $z$ were negative. The functions most at risk are `fixed_div_floor` and `fixed_div_ceil`, as they often use non-constant numbers as the divisor $z$ in `m
O3 Security · Impact-Aware SCA

Is GHSA-x5m4-43jf-hh65 in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works
soroban-fixed-point-math has Incorrect Rounding and…