XRPXRP, coin
DisputedSecurity

AI security agent discovers decade-old XRP Ledger overflow bug; emergency patch deployed

Veria Labs' AI agent found a critical integer-overflow flaw in XRP Ledger's payment engine that could have allowed minting trillions of XRP beyond the 100 billion supply cap; developers issued an emergency fix on September 25 with no evidence of exploitation.

Why it matters

The incident reveals a fundamental supply-cap vulnerability persisted undetected for over a decade in a top-10 cryptocurrency, and was only found by AI-assisted analysis rather than human audits. The emergency bypass of normal governance procedures highlights tension between responsible disclosure and network security.

Where the sources disagree

Maximum XRP minting potential

18 trillion XRP in a single transaction

CryptoSlate, Crypto.News

billions of XRP requiring hundreds of transactions

CoinDesk

unlimited tokens

Finbold

CryptoSlate and Crypto.News report 18 trillion XRP via a single transaction, CoinDesk says billions via hundreds of transactions, Finbold says unlimited tokens

Key facts

An AI security agent from Veria Labs discovered a critical integer-overflow bug in the XRP Ledger payment engine

Reported by CryptoSlate

The vulnerability could have allowed minting approximately 18 trillion XRP through a single crafted transaction

18,000,000,000,000 tokensDisputed figureReported by CryptoSlate

The bug required hundreds of carefully constructed transactions to manipulate costs to near-zero while paying sellers in full

Disputed figureReported by CoinDesk

The vulnerability was reported on September 22 and patched three days later on September 25

Reported by CryptoSlate

More than 80% of default validators upgraded to xrpld 3.4.1 by September 25

80 %Reported by Crypto.News

No unauthorized XRP was created and no exploitation occurred on public networks

Reported by CryptoSlate

What happened

Security researcher Cayden Liao and Veria Labs' autonomous AI agent uncovered an 11-year-old integer-overflow vulnerability in the XRP Ledger's payment engine that could have permitted creation of XRP beyond the protocol's 100 billion token cap. The flaw was reported internally on September 22 and patched three days later in version 3.4.1, with more than 80% of default validators upgrading by September 25. RippleX and the XRP Ledger Foundation confirmed no unauthorized XRP was created and no exploitation occurred on public networks. Veria Labs and Liao received the maximum $250,000 bug bounty. Public disclosure followed on October 9. Sources differ on the exact minting potential and the transaction complexity required to trigger the bug.

How the story developed

  1. Update

    Vulnerability discovered by Veria AI agent

    Autonomous AI security system analyzed rippled codebase and identified integer-overflow flaw

    CryptoSlate

  2. Update

    Internal report submitted to XRP Ledger developers

    Cayden Liao and Veria Labs reported the vulnerability through responsible disclosure channels

    CryptoSlate

  3. Resolution

    Emergency patch version 3.4.1 released

    RippleX deployed fix bypassing normal governance process; 80%+ of default validators upgraded same day

    CryptoSlate

  4. Update

    Batch validation fix activated

    Separate fix originally planned for earlier rollout activated after validator delays

    Crypto.News

  5. Official statement

    Public disclosure by XRP Ledger Foundation and RippleX

    Official confirmation of vulnerability, fix, and no exploitation evidence; $250,000 bug bounty awarded

    CryptoSlate

  6. First report

    First report by CryptoSlate

    AI discovers XRP Ledger flaw that could mint 18 trillion tokens and put $94 billion market at risk

    CryptoSlate

  7. Independent corroboration

    Independently corroborated by Crypto.News

    XRP Ledger confirms 100B supply is safe after major security flaw

    Crypto.News

How coverage built up

Independent sources over time, counted the way the consensus panel counts them: a republication of a wire story does not move the line.

11 Oct, 10:305 independent sources12 Oct, 11:53
  • 11 Oct 2026, 10:30 UTC: CryptoSlate — 1 independent source, 1 reports
  • 12 Oct 2026, 04:30 UTC: Crypto.News — 2 independent sources, 2 reports
  • 12 Oct 2026, 08:32 UTC: CoinDesk — 3 independent sources, 3 reports
  • 12 Oct 2026, 08:37 UTC: Bitcoin Insider — 4 independent sources, 4 reports
  • 12 Oct 2026, 11:53 UTC: Finbold — 5 independent sources, 5 reports

Affected entities

Original sources