On October 9, 2026, the XRP Ledger project disclosed a payment engine bug that could have let an attacker create spendable XRP. A security researcher reported it on September 22. The emergency release xrpld 3.4.1 fixed it on September 25, without an amendment vote. The disclosure says it found no evidence anyone exploited the bug on a public network.
Before and after the patch
| Aspect | xrpld 3.4.0 and earlier | xrpld 3.4.1 |
|---|---|---|
| Offer totals in one payment | Summed in a 64-bit integer with no overflow check | Overflow checks in effect |
| Safety check for new XRP | Used the same unchecked arithmetic, so it missed the problem | Covered by the fix |
| Amendment vote needed | Not applicable | No, the checks took effect with the release |
| Status after Oct 9 | Reported to be amendment-blocked | More than 80% of default trusted validators upgraded on Sept 25 |
How the bug worked
When one payment consumes several offers on the ledger’s built-in exchange, the payment engine adds up the XRP amounts in a 64-bit integer. The code did not check for overflow. If the total passed the maximum value, it wrapped around to a small number. Offer owners were paid in full, but the payer was charged only the wrapped total. The difference was XRP that did not exist before.
A safety check meant to catch newly created XRP used the same unchecked arithmetic, so it also missed the problem. Reports say the flaw dates to the original payment engine, around 2015, though one analysis dates the related invariant to 2017. It went unnoticed for about a decade.
Exploiting it was not simple. Reports describe a setup of roughly 256 funded accounts with specially priced offers, at a cost of a few hundred XRP in reserves and fees, most of it recoverable. Normal payments could not trigger it.
Who found it and how it was fixed
Cayden Liao and Veria AI reported the bug through the XRPL bug bounty on September 22. Initially rated Major, it was raised to critical after RippleX reproduced it on a standalone server. The fix landed in the 3.4.1 release branch on September 23 and xrpld 3.4.1 shipped on September 25. The public disclosure report followed on October 9. These dates come from CryptoTicker, Noze, Crypto Briefing and AltcoinBuzz, which relay the XRPL.org disclosure. We could not open the XRPL.org report itself.
The 3.4.1 source code was not published at release because of its security sensitivity, according to AltcoinBuzz, which means validators ran the patch before the public could read it. That is a common practice for urgent security fixes.
Veria says its AI agent identified the flaw and built a proof of concept on a local network, which a person then validated. The XRPL.org report as relayed does not say how the bug was found. Treat the AI discovery claim as the vendor’s account, not independently verified. The proof of concept ran on a local network, not the live ledger, so no demonstration on the live ledger is reported.
Who Benefits and How
The benefit is indirect. If you hold XRP, the patch protects the supply from this particular bug and you don’t need to do anything. Server operators and validators need xrpld 3.4.1 or newer, and it is already out. Holders do not need to move funds.
Where it falls short
Some outlets cite a figure of about 18 trillion XRP for what one transaction might have minted. We could not find that number in the disclosure summaries we opened. They say only that it could exceed the total supply, which is 99.99 billion XRP (about 63.13 billion circulating, per CryptoTicker). Veria states it received a $250,000 bounty, but the relayed disclosure and other outlets do not give an amount, so that is unconfirmed. “No evidence of exploitation” is the project’s finding, not proof that no one tried. The disclosure also reports a second finding: Batch inner transactions were not checked for a required wrapper field in versions 3.3.0 and 3.4.0. It was fixed by fixBatchV1_2, and no funds were lost. Claims that the bug could have crashed XRP’s price or retirement funds are speculation. Nothing we read measures that risk.
Frequently Asked Questions
Was any XRP actually created?
The project says it found no evidence of exploitation on any public network, and no lost funds or consensus problems tied to the bug.
Do I need to update anything as a holder?
No. Server operators and validators need xrpld 3.4.1 or newer. Holders do not need to move funds.
Why was there no amendment vote?
The overflow checks took effect with the 3.4.1 release, according to the disclosure summaries. That is why it moved faster than a normal amendment.
How old is the bug?
The disclosure says it was probably present since 2015.
Sources
- CryptoTicker: XRP Ledger Closes a 2015 Flaw That Could Create XRP Out of Nothing (Oct 10, 2026)
- Noze: XRP Ledger: payment engine overflow and the role of AI (accessed Oct 13, 2026)
- Crypto Briefing: XRP Ledger discloses overflow bug that could have minted XRP beyond its supply cap (Oct 10, 2026)
- KuCoin News: Ripple Discloses Two Vulnerabilities in xrpld 3.4.1 (accessed Oct 13, 2026)
- AltcoinBuzz: XRP Ledger Fix Wins Every Validator Vote, Activates Oct 9 (Oct 6, 2026)
