CVE-2026-61694

go-xrpl: ParseMPTAmountBinary: positive MPT amount silently decoded as negative (int64 wrap)

Published Oct 30, 2026 CVSS 3.1 · 3.7 Low EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade go‑xrpl to a version that incorporates commit 9dbd3935ed6c54f0232f2291edf9c012a0900dd5 or later.
  • If the upgrade cannot be performed immediately, add a bounds check after parsing MPT amounts to ensure the magnitude is less than 2^63; reject or correct any values outside this range before use.
  • Audit downstream code that uses EscrowData.MPTAmount and validate that all calculations are robust against negative or out‑of‑range values, and align with rippled’s expected behavior.

Generated by OpenCVE AI on October 30, 2026 at 21:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Lejamon
Lejamon go-xrpl
Vendors & Products Lejamon
Lejamon go-xrpl
Type Values Removed Values Added
Description 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.
Title go-xrpl: ParseMPTAmountBinary: positive MPT amount silently decoded as negative (int64 wrap)
Weaknesses CWE-190
References
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-190

    Integer Overflow or Wraparound

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 6, 2026, 5:58 PM
Reserved
Jul 10, 2026, 6:36 PM
Status
Deferred
Published
Oct 30, 2026, 8:17 PM
Modified
Nov 6, 2026, 6:18 PM