XRP Ledger Patch Fixes Payment Engine Vulnerability That Could Create 1.84 Trillion XRP

The XRP Ledger (XRPL) payment engine vulnerability, which could bypass XRP issuance limits and create approximately 18.45 trillion XRP in a single transaction, has been patched. XRPL developers stated there is no evidence the vulnerability was exploited on the public network.
XRPL urgently deployed server software 'xrpld' version 3.4.1 on September 25. According to an October 9 report, the payment engine could miscalculate total XRP required when processing multiple decentralized exchange orders due to an integer overflow. Attackers could have created and used new XRP through specially configured orders and single payments.
The XRPL report suggested the flaw may have existed since 2015, when the payment engine was written. Security firm Veria Labs estimated that exploitation could create around 18.45 trillion XRP in a single transaction—exceeding the initial 10 billion XRP issuance cap by 184 times—but this represents only potential creation, not actual issuance or network damage.
The error occurred during summing payment amounts for multiple orders; if the total exceeded integer limits, calculations would return lower values, allowing sellers to receive full payments while buyers paid significantly less XRP. A ledger validation check also had a separate arithmetic error that could prevent transaction rejection, according to XRPL's report.
Veria Labs reported the vulnerability on September 22, and the fix was implemented the next day. XRPL deployed version 3.4.1 on September 25, with over 80% of default validators switching to the new version the same day. Veria Labs explained that an AI security agent discovered the flaw and created working attack code in a test environment.
The patch was applied differently from standard protocol changes. Typically, protocol updates require validator consensus before activation after a period, but this overflow fix was immediately applied upon server upgrade. XRPL stated they chose urgent deployment to avoid network exposure during the standard process, as public disclosure of the fix would leave the vulnerability open until protection was complete.
Version 3.4.1 also included fixes for another batch transaction flaw, which was activated on October 9 via a separate procedure. The XRP overflow patch was applied alongside server updates, while the batch transaction fix required its own activation process. This incident prevented potential overlap of payment calculation errors and cap protection mechanisms, without exceeding supply limits in practice.
Korean Source
This article is an English localization of a Korean-language crypto news report. Original headline: XRP 18조개 생성 가능한 결제 취약점 패치됐다