Technical impact
The vulnerability is in the Go‑xrpl implementation of the XRP Ledger protocol. In versions through June 18 2026 the ParseMPTAmountBinary routine converts an eight‑byte magnitude to a signed 64‑bit integer without ensuring it fits in the 63‑bit signed range. If the magnitude is 2^63 or larger, the conversion silently wraps into a negative value, producing a wrong amount. The error propagates to EscrowData.MPTAmount and readMPTAmount, causing downstream calculations and ledger entries to diverge from the reference rippled server. This creates a data‑integrity issue where amounts may be reported as negative or incorrectly large, affecting escrow balance calculations.
Affected Systems
This flaw affects the go‑xrpl library maintained by LeJamon. Versions up to and including the June 18 2026 release are vulnerable. The fix was introduced in commit 9dbd3935ed6c54f0232f2291edf9c012a0900dd5 and is available in later releases.
Risk and Exploitability
The CVSS score of 3.7 indicates low severity, and the EPSS score is not available. The vulnerability is not listed in CISA’s KEV catalog. The likely attack vector is inferred: an attacker would need to supply ledger or transaction data that includes an MPT amount with a magnitude beyond 2^63−1. This may be possible when the application processes untrusted data, such as imported ledger entries or crafted escrow transactions. Because the error is silent, a malicious payload could cause the application to record an incorrect negative amount, potentially leading to financial loss or misreporting.