go-xrpl: ParseMPTAmountBinary: positive MPT amount silently decoded as negative (int64 wrap)
Affects go-xrpl through revision 0.0.0-20260618134614-cb77d640ee26 when a 33-byte MPT amount is parsed, including MPT escrow sfAmount fields. Fixed in 0.0.0-20260624143208-9dbd3935ed6c.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 0.0.0-20260624143208-9dbd3935ed6c
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- LeJamon go-xrpl
through 0.0.0-20260618134614-cb77d640ee26
References 3
GitHub · LeJamon/go-xrpl
Questions about CVE-2026-61694
What does this mean?
A positive MPT amount of at least 2^63 is decoded as a negative number because of a 64-bit integer wrap. This can make a go-xrpl node read an MPT escrow entry differently from rippled, which can lead to ledger-state divergence.Source: github.com
Am I affected, and how do I check?
Affected are go-xrpl revisions through 0.0.0-20260618134614-cb77d640ee26. The bug is reached when a 33-byte MPT amount is parsed, including through ParseEscrow for sfAmount fields. Check the go-xrpl revision your build uses against that version.Source: github.com
What should I do about it?
Upgrade go-xrpl to revision 0.0.0-20260624143208-9dbd3935ed6c or later, which contains the fix.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data