PT-2026-134174
CVE-2026-61694
·
Published
2026-10-30
·
Updated
2026-10-30
Description by
CVSS 3.1
3.7
LowMetricsAV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Name of the Vulnerable Software and Affected Versions
go-xrpl versions prior to the June 18, 2026 revision
Description
The software contains inconsistencies in how it handles MPT magnitudes. The
ParseMPTAmountBinary() function in internal/ledger/state/ripple state.go uses num.Int64() to convert eight-byte MPT magnitudes without verifying if they fit within 63 bits, which allows positive magnitudes of 2^63 or greater to wrap into negative amounts without triggering an error. This affects the ParseEscrow() function, which processes 33-byte sfAmount fields and stores MPTRaw() in EscrowData.MPTAmount, leading to incorrect calculations and divergence from rippled interpretations. Additionally, the readMPTAmount() function in internal/tx/ledgerfields/decode stream.go accepts magnitudes that exceed limits and produces large decimal strings because it does not enforce the maximum signed 64-bit value, creating a discrepancy with the safer public codec in codec/binarycodec/types/amount.go.Recommendations
Update to the revision released on June 18, 2026, or apply the fix from commit 9dbd3935ed6c54f0232f2291edf9c012a0900dd5.
Exploitability
Exploit
Fix
Impacts
Vendors
Affected products
Found an issue in the description? Have something to add? Feel free to write us 👾