CVE-2026-24783

7.5

Script3 · soroban-fixed-point-math

The soroban-fixed-point-math library incorrectly handles signed division in the mulDiv function, leading to incorrect rounding results in smart contract mathematical operations.

Executive summary

A vulnerability in the soroban-fixed-point-math library allows for incorrect mathematical calculations in smart contracts, potentially resulting in significant financial integrity issues.

Vulnerability

The vulnerability exists within the mulDiv(x, y, z) function, where the logic fails to account for the sign of the divisor when both the intermediate product and the divisor are negative. This flaw affects core functions like fixed_div_floor and fixed_div_ceil, and it is exploitable by any unauthenticated actor capable of interacting with the affected smart contract.

Business impact

The integrity of financial calculations within Soroban smart contracts is compromised by this flaw. Successful exploitation could lead to incorrect asset distribution, balance errors, or the failure of automated financial logic, which directly impacts the reliability of decentralized applications. With a CVSS score of 7.5, this high severity rating reflects the potential for significant unauthorized manipulation of transaction outcomes despite the lack of direct data exfiltration.

Remediation

Immediate Action: Update the soroban-fixed-point-math dependency to version 1.3.1 or 1.4.1 immediately to incorporate the necessary logic fixes.

Proactive Monitoring: Review smart contract transaction logs for anomalous output values or unexpected rounding behavior in mathematical operations.

Compensating Controls: Since no workarounds exist, developers should perform a thorough audit of all smart contracts utilizing this library to identify potential impacts on current contract logic.

Exploitation status

Public Exploit Available: No (exploit_available: unknown)

Analyst recommendation

Given the critical role of fixed-point math in financial smart contracts, this vulnerability presents a high risk to application integrity. Administrators and developers must prioritize upgrading to the patched versions 1.3.1 or 1.4.1 to prevent potential manipulation of contract execution results. Immediate action is required to ensure the continued security and accuracy of affected Soroban-based systems.

Sources