# XRP Ledger Discloses Decade-Old Overflow Bug That Could Have Created XRP Beyond Its 100 Billion Cap

RippleX shipped the fix on September 25 without saying what it repaired and skipped the usual validator amendment vote, then disclosed the flaw on October 9 and said it found no evidence of exploitation.

- Published: 2026-10-11T05:46:49.306Z
- Canonical: https://polylog.news/crypto/2026-10-11/xrp-ledger-discloses-decade-old-overflow-bug-that-could-have
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [CoinDesk](https://www.coindesk.com/tech/2026/10/10/xrp-ledger-patched-decade-old-bug-that-could-create-billions-of-dollars-in-xrp-from-nothing), [Polylog editors](https://polylog.news), [crypto.news](https://crypto.news/evernorth-completes-merger-with-473m-xrp-nasdaq-debut/), [Crypto Briefing](https://cryptobriefing.com/xrp-ledger-overflow-bug-extra-xrp/)

Researchers showed that a single payment on the XRP Ledger could [create spendable XRP that the sender never funded](https://www.coindesk.com/tech/2026/10/10/xrp-ledger-patched-decade-old-bug-that-could-create-billions-of-dollars-in-xrp-from-nothing). The demonstration led to an emergency software release. The flaw had been in the code [since 2015](https://t.me/BWEnews/16529).

The bug existed in the payment engine that matches trades against the ledger's built-in order book. An attacker could open hundreds of accounts, and each account would post an offer to give a tiny amount of some token in return for an unusually large amount of XRP. A specially built payment could then consume all of those offers in one pass. The engine added up the XRP the buyer owed in a 64-bit integer. According to the [RippleX disclosure summarized by Crypto Briefing](https://cryptobriefing.com/xrp-ledger-overflow-bug-extra-xrp/), that sum could overflow, so the ledger would credit XRP that no one had paid in. This is an arithmetic overflow, a logic error in core protocol code. It is not a smart-contract flaw.

RippleX, Ripple's engineering arm, shipped the fix in xrpld version 3.4.1 on September 25 and did not describe what it repaired. It published the full disclosure on October 9. Changes to XRP Ledger rules normally go through an amendment process in which validators vote before a change takes effect. This fix went out as an ordinary software update and skipped that vote. RippleX says it has [found no evidence that anyone used the flaw](https://www.kucoin.com/news/flash/xrp-ledger-emergency-patch-addresses-minting-bug).

The disclosure came as a large holder of XRP prepared to list in the United States. Evernorth completed its merger with Armada Acquisition Corp. II and [holds about 473 million XRP](https://crypto.news/evernorth-completes-merger-with-473m-xrp-nasdaq-debut/), with gross cash proceeds of about $300 million and Nasdaq trading expected on October 12. A treasury company's valuation rests on the fixed supply of the asset it holds. A flaw that could have broken that cap goes to the core of the investment case.

The quiet patch was a sound security decision, because announcing the bug before validators upgraded would have shown attackers how to use it. It also shows how this ledger works in practice. One engineering organization found the flaw, wrote the fix, and decided when to tell the public. The validator vote, which is the decentralized part of the process, was bypassed.

## What this means

The mechanism here is supply integrity. A ledger that sells itself on a hard 100 billion XRP cap carried a path to unbacked issuance for about ten years, and people outside the Ripple orbit did not find it. The parties exposed are XRP treasury vehicles such as Evernorth, issuers of XRP exchange-traded products, and anyone who models XRP as having a fixed supply. Each of them now has to account for governance as well as code. The market has priced the patch, since there is no evidence of exploitation. It has not priced the precedent that rule-level changes can ship without the amendment vote when the developer judges the case urgent. A close precedent is Bitcoin's 2018 inflation bug (CVE-2018-17144), which developers also patched quietly before full disclosure. That episode led to stronger review practices without lasting damage to the asset's credibility. The likelier outcome over the coming months is that more review attention, much of it AI-assisted, turns to older ledger code bases and produces further disclosures of this kind. The read would be wrong if independent audits of xrpld find no comparable defects by the end of the year, which would suggest this bug was an isolated case.

## What to watch

- Whether independent researchers publish a full on-chain review confirming that no account's balance ever exceeded what it was funded with. RippleX's statement is so far the only evidence.
- How XRP Ledger validators respond to an emergency fix that skipped their amendment vote. Formal objections would show how much real independence the validator set has.
- Evernorth's first days of trading on Nasdaq and how its disclosures treat protocol risk, which would show whether investors in the treasury company now price supply-integrity risk.