AI · Bitcoin.com News
The problem sat inside the code that settles payments across the XRP Ledger’s built-in decentralized exchange (DEX)
Compiled by KHAO Editorial — aggregated from 1 source. See llms.txt for citation guidance.
◌ Single Source
By pushing that sum high enough, it “wrapped around,” which is what an integer overflow does.
Key facts
- The XRPL Operations account has since made 3.4.1 the minimum required version, adding
- The disclosure landed in an ugly week for crypto security as Ledger device losses, which Bitcoin.com News reported, reached an estimated $93.4M
- Lastly, Ripple-backed Evernorth is preparing to start trading on Nasdaq under XRPN on Monday, with roughly 473 million XRP on its books
- The XRP Ledger quietly patched a 2015-era payment engine flaw that could have let an attacker create spendable XRP beyond the network’s fixed supply for a few hundred XRP in reserves
Summary
The XRP Ledger quietly patched a 2015-era payment engine flaw that could have let an attacker create spendable XRP beyond the network’s fixed supply for a few hundred XRP in reserves. Cayden Liao and Veria AI initially reported the XRPL overflow bug through the bug bounty program on Sept. 22, 2026. RippleX rated the flaw critical, and over 80% of default UNL validators ran the xrpld 3.4.1 fix by Sept. 25. The XRPL disclosure on Oct. 9 found no exploit, as the fixBatchV1_2 amendment went live the same day. The problem sat inside the code that settles payments across the XRP Ledger’s built-in decentralized exchange (DEX).