Skip to content

← Public intelligence

crates.io package

soroban-fixed-point-math

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5crates.ioPublished

    soroban-fixed-point-math has Incorrect Rounding and Overflow Handling in Signed Fixed-Point Math with Negatives

    CVE-2026-24783 · GHSA-x5m4-43jf-hh65

    Affected
    • crates.io soroban-fixed-point-math >= 1.4.0, <= 1.4.0; >= 1.3.0, <= 1.3.0
    Fixed in
    1.4.11.3.1· Vendor fix available
    Issue
    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 fixeddivfloor and fixeddivceil, 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…

    Recommended action: Upgrade to 1.4.1 or 1.3.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →