LeJamon go-xrpl up to 0.0.0-20260618134614-cb77d640ee26 MPT Amount Decoder ripple_state.go ParseMPTAmountBinary integer overflow

Summaryinfo

A vulnerability has been found in LeJamon go-xrpl up to 0.0.0-20260618134614-cb77d640ee26 and classified as problematic. The affected element is the function ParseMPTAmountBinary of the file internal/ledger/state/ripple_state.go of the component MPT Amount Decoder. Performing a manipulation results in integer overflow. This vulnerability is cataloged as CVE-2026-61694. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to install a patch to address this issue.

Detailsinfo

A vulnerability was found in LeJamon go-xrpl up to 0.0.0-20260618134614-cb77d640ee26. It has been classified as problematic. This affects the function ParseMPTAmountBinary of the file internal/ledger/state/ripple_state.go of the component MPT Amount Decoder. The manipulation with an unknown input leads to a integer overflow vulnerability. CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. This is going to have an impact on integrity. The summary by CVE is:

go-xrpl is a Go implementation of the XRP Ledger protocol. In versions through the June 18, 2026 revision identified by the advisory, `ParseMPTAmountBinary` in `internal/ledger/state/ripple_state.go` converts the eight-byte MPT magnitude using `num.Int64()` without checking that it fits in 63 bits. A positive magnitude of at least 2^63 silently wraps into a negative amount without an error. `ParseEscrow` passes 33-byte `sfAmount` fields to the parser and stores `MPTRaw()` in `EscrowData.MPTAmount`, causing incorrect downstream calculations and divergence from rippled's interpretation of the same escrow entry. Independently, `readMPTAmount` in `internal/tx/ledgerfields/decode_stream.go` accepts over-limit magnitudes and surfaces large decimal strings without enforcing the maximum signed 64-bit value. The public codec in codec/binarycodec/types/amount.go already rejects these values, leaving the internal decoders inconsistent with that safe path. A source fix is available in commit 9dbd3935ed6c54f0232f2291edf9c012a0900dd5.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-61694 since 07/10/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available.

Applying the patch 9dbd3935ed6c54f0232f2291edf9c012a0900dd5 is able to eliminate this problem.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• LeJamon

Name

• go-xrpl

Version

• 0.0.0-20260618134614-cb77d640ee26

Website

• Product: https://github.com/LeJamon/go-xrpl/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion