RippleX patches decade-old XRP Ledger bug threatening 100 billion token cap

• An integer-overflow vulnerability in the payment engine could have allowed attackers to create unlimited XRP without detection, unnoticed since approximately 2015.
• RippleX deployed the fix in version 3.4.1 on September 25 without the customary two-week validator vote required for protocol changes.
• More than 80% of default validators upgraded before the fix’s code was made public, allowing RippleX to patch the bug before disclosure.

• 10 years Estimated time the integer-overflow bug remained undetected in XRP Ledger code
• 100 billion XRP supply cap that faced potential breach from the vulnerability
• 3.4.1 Server version that deployed the emergency fix on September 25, 2026

A security report disclosed a critical flaw in the XRP Ledger’s payment processing software that could have enabled attackers to mint new XRP tokens indefinitely. Researcher Cayden Liao and Veria AI reported the bug through the XRPL Bug Bounty program on September 22, 2026, after which RippleX, Ripple’s developer arm, released a fix three days later. According to the disclosure, the vulnerability affected xrpld 3.4.0 and earlier, though RippleX found no evidence the flaw was ever exploited.

Attackers could overflow payment counter to bypass supply rules

The XRP Ledger operates a built-in decentralized exchange where accounts post offers to trade one asset for another.

The vulnerability lay in how the ledger tracked these trades: an attacker could create hundreds of accounts, each offering minuscule amounts of a token in exchange for large quantities of XRP. When a single payment executed all offers simultaneously, the ledger’s counter for tracking XRP debits would overflow, mathematically rolling past its limit like an odometer at 999,999 miles, and reset to near zero.

The selling accounts would be paid in full; the buyer would pay almost nothing.

The safety check designed to detect newly created XRP relied on the same counter, so it failed to catch the arithmetic gap. Because no funds changed hands at their stated prices, the exploit would generate XRP tokens out of thin air without triggering the ledger’s supply validation logic.

RippleX skipped mandatory validator vote to prevent public code disclosure

XRP Ledger protocol changes normally require approval from more than 80% of trusted validators, the servers that confirm transactions, and must remain open for two weeks before activation. RippleX invoked an extraordinary exception and released the fix in version 3.4.1 on September 25 without awaiting a public vote or the standard review period. More than 80% of default validators upgraded on release day, before the fix’s code was published openly. According to the official vulnerability report, “This is the first time a change to transaction processing has deliberately shipped this way since the amendment system was introduced more than ten years ago.”

RippleX justified the bypass by arguing that a public vote would have exposed the bug in readable code while it remained exploitable. The XRPL Foundation, RippleX, and validators jointly approved the approach.

RippleX stated that future changes would continue to follow the standard amendment process, positioning the September fix as a singular emergency measure rather than a shift in governance practice.

Governance precedent collides with decentralization claims days after Ripple debate

The timing of the disclosure amplified concerns about XRP Ledger’s decentralization. The vulnerability report was published on October 9, 2026, a day after Cyber Capital founder Justin Bons had challenged Ripple’s David Schwartz during an XRP debate, calling the platform’s claims of decentralization “fraud.” Bons cited centralization risks; Schwartz defended the ledger’s validator network.

The emergency fix now posed a substantive question about that decentralization claim. While RippleX, the XRPL Foundation, and validators collectively decided to bypass the vote, the decision was made among a small group with advance knowledge of a critical flaw, conditions that did not apply to ordinary amendments.

No public mechanism allowed other stakeholders to weigh in on whether the bug’s severity justified overriding the governance rule, and no precedent existed for validators to assess similar situations in the future.

The CCS read. Ripple’s emergency governance move worked tactically, the bug is patched and no funds were lost, but it weakens institutional confidence in the ledger’s amendment process. Token holders were not consulted, and the exception sets a precedent that centralized decision-makers can invoke unilaterally in the name of security. Future institutional investors assessing XRP Ledger’s governance will now factor in that the 80% validator rule can be suspended when those with early warning decide it should be.

The XRPL Foundation and RippleX have not announced whether they will propose formal rules governing when future emergency bypasses may occur, or how validators and the community might challenge such decisions. The ledger’s amendment voting process remains unchanged, but the question of whether a security crisis that repeats, or a non-security upgrade that RippleX deems urgent, will follow the same shortcut remains unresolved.

Original reporting: beincrypto.com