A researcher surfaced a critical integer-overflow vulnerability in the XRP Ledger's payment engine in September, a flaw RippleX engineers confirmed had lived in the codebase since 2015. The maintainers disclosed the issue Friday and shipped a fix in version 3.4.1 on Sept. 25, with more than 80% of the network's trusted validators running the patched software the same day.

The maintainers wrote that there is no evidence of exploitation on the mainnet. The same flawed arithmetic powered both the payment engine and the ledger's built-in check that is supposed to prevent XRP creation, the team added.

What did the vulnerability actually do?

The bug lived in the payment engine, the layer of the XRP Ledger software that processes transactions and consumes offers from the on-chain order book. When a single payment drained hundreds of specially crafted offers, the sum of what the buyer owed exceeded the maximum value the system could store. The integer wrapped around to a tiny number, the maintainers explained.

RippleX engineers said the engine paid each seller in full but charged the buyer almost nothing. The difference amounted to newly minted XRP that should never have existed. An attacker could have traded, moved or deposited the forged tokens on centralized venues, the team warned.

Why didn't the network's safety check catch it?

The ledger's built-in check, designed to confirm that no transaction creates XRP, relied on the same flawed arithmetic. It wrapped around identically and returned a passing result, the maintainers said.

That double failure kept the flaw dormant for roughly a decade. RippleX engineers noted that no ordinary payment comes anywhere near triggering the overflow, which is why it escaped detection from 2015 until the bug bounty report arrived in September.

How was the patch rolled out?

Maintainers bypassed the ledger's standard amendment process, which requires validators to vote and wait two weeks before a change takes effect. The disclosure marks the first time a transaction-processing change shipped that way since the system launched.

The maintainers said the severity justified the unusual move. Walking through the standard process would have left the open-source fix visible and the bug exploitable for two more weeks. More than 80% of trusted validators adopted v3.4.1 on the day it shipped, Sept. 25.

Could the bug have been exploited?

There is no evidence the vulnerability was ever triggered on the network, the team said.

The disclosure echoes a counterfeiting scare that hit Zcash this year, when developers raced to patch a soundness bug in the privacy coin's shielded pool that could have allowed forged coins. That episode sent ZEC tumbling before the network's Ironwood upgrade resolved it.

What's the operational fallout?

The disclosure itself requires no user action. The patched validator software cleared more than 80% of network adoption the day it shipped, closing the window for active exploitation within hours.

XRP traded at $1.38 on Monday, down 1.6% over 24 hours and off 9.4% over the prior seven days, the worst performance among major cryptocurrencies over both windows.

The maintainers' bypass of the standard amendment process will draw closer scrutiny from the XRP Ledger governance community. It marks the first time a transaction-processing change shipped outside the two-week voting window, and the episode will likely push RippleX to formalize emergency-patch procedures before the next critical flaw surfaces.