Nature of the Bug
Published 10/12/2026, 12:40:21 AM
The bug was a decade-old integer overflow vulnerability in the XRP Ledger's (XRPL) payment engine that could theoretically have allowed an attacker to mint up to 18.45 trillion XRP in a single transaction—completely bypassing the network's hard-capped 100 billion supply. Discovered by AI security firm Veria Labs in September 2026 through a bug-bounty program Gaming Report, it was fixed in an emergency patch without a validator voteley, and developers found no evidence the bug was ever exploited on a public network.
Nature of the Bug
The flaw lived in the XRPL payment engine and involved an integer overflow. When a single payment filled many order-book offers, the XRP total could "wrap around" to a much smaller number, meaning sellers could receive large XRP credits while the buyer paid very little—effectively creating spendable XRP from nothing. [Source: https://www.binance.com/en/square/post/375709855646390] The overflow bypassed XRPL's supply safeguards, allowing minting beyond the fixed 100 billion XRP cap. [Source: https://cryptobriefing.com/xrp-ledger-overflow-bug-extra-xrp]
Scale of the Potential Impact
- Veria Labs estimated the vulnerability could mint 18.45 trillion XRP in a single transaction—more than 184x the original 100 billion total supply. [Note: not independently confirmed] [Source: https://www.aol.com/articles/ai-uncovers-xrp-ledger-bug-140044000.html] [Source: https://www.tradingview.com/news/u_today:0c230b8f7094b:0-ripple-warns-about-ai-threat-following-bug-that-could-have-created-billions-of-xrp]
- At the time of disclosure, XRP's market value stood at roughly $94 billion, which represented the total value at risk. [Source: https://cryptoslate.com/ai-discovers-xrp-ledger-flaw-that-could-mint-18-trillion-tokens-and-put-94-billion-market-at-risk]
Timeline and Discovery
- The flaw is believed to date back to 2015 and affected xrpld versions 3.4.0 and earlier. [Source: https://www.coindesk.com/tech/2026/10/10/xrp-ledger-patched-decade-old-bug-that-could-create-billions-of-dollars-in-xrp-from-nothing] [Source: https://cryptobriefing.com/xrp-ledger-overflow-bug-extra-xrp]
- It was found by researcher Cayden Liao and Veria AI (AI security startup Veria Labs) and internally reported on September 22, 2026 via a bug-bounty program. [Source: https://www.coindesk.com/tech/2026/10/10/xrp-ledger-patched-decade-old-bug-that-could-create-billions-of-dollars-in-xrp-from-nothing] [Source: https://www.theblock.co/news/ecosystems/2026-10-11-xrp-ledger-patches-decade-old-bug-that-could-have-minted-trillions-of-xrp-418230]
- RippleX fixed it on September 25, 2026 in xrpld 3.4.1, as an emergency release that skipped the normal validator vote. [Source: https://www.theblock.co/news/ecosystems/2026-10-11-xrp-ledger-patches-decade-old-bug-that-could-have-minted-trillions-of-xrp-418230] [Source: https://thedefiant.io/news/security/xrp-ledger-discloses-decade-old-bug-that-could-mint-trillions]
- The disclosure was made public around October 9–10, 2026. [Source: https://cryptobriefing.com/xrp-ledger-overflow-bug-extra-xrp]
Exploitation Status
Developers found no evidence the bug was exploited on a public network. [Source: https://thedefiant.io/news/security/xrp-ledger-discloses-decade-old-bug-that-could-mint-trillions] [Source: https://phemex.com/news/article/xrp-ledger-patches-critical-minting-bug-that-could-have-created-1845-trillion-tokens-99473] RippleX Engineering Lead J. Ayo Akinyele confirmed the payment engine contained the severe, decade-long vulnerability and that it was discovered through the bug bounty program. [Source: https://www.kucoin.com/news/flash/ripplex-engineer-critical-10-year-xrp-ledger-vulnerability-discovered-and-fixed] [Verified by independent sources: https://www.rootdata.com/news/785115]
Conclusion
In short, the bug was an integer overflow in the XRP Ledger's payment engine, discovered by Veria Labs, that could have minted up to 18.45 trillion XRP but was patched in September 2026 without being exploited. The exact code-level exploit mechanics (how the wrap-around was precisely triggered) remain described in secondary summaries rather than a primary technical write-up, so that precise detail is not fully confirmed.