The XRP Ledger Foundation has disclosed a serious payment-engine flaw that could have created spendable XRP through a deliberately engineered trade. The Foundation says there is no evidence the vulnerability was exploited on any public network, and the fix shipped before the details were made public.
What the bug could do
A payment that consumed hundreds of specially priced order-book offers could overflow the software’s integer arithmetic. In the vulnerable versions, the ledger could have credited sellers with the full XRP amounts while charging the buyer only a wrapped, much smaller total. That could have created XRP that could then be spent. The attack required crafted offers and a payment designed to consume them; the report says ordinary payments and trades could not trigger it accidentally.
Patch came before public disclosure
A researcher reported the issue on September 22. RippleX reproduced it, confirmed the resulting XRP could be spent, and included overflow checks in xrpld 3.4.1, released September 25. The XRP Ledger Foundation published its detailed disclosure on October 9. It says more than 80% of default UNL validators had upgraded to 3.4.1 or later on release day. The new checks reject an overflowing payment and widen a separate supply invariant so similar arithmetic cannot silently wrap.
The same disclosure covers a separate Batch transaction validation flaw. Its fix, fixBatchV1_2, activated on the XRP Ledger mainnet on October 9, before BatchV1_1 was enabled. The report says no mainnet funds or transactions were affected by that second issue.
This is a disclosure of a patched vulnerability, not a report of XRP being stolen or newly created on the live network. Node operators should follow the Foundation’s upgrade guidance. The full technical explanation is available in the XRP Ledger Foundation disclosure; CoinDesk also reported on the disclosure.


Leave A Comment