would

<p>The XRP Ledger disclosed on October 9 an integer-overflow vulnerability in its payment engine that could have allowed specially crafted transactions to create spendable XRP beyond the network’s intended supply cap. The disclosure followed an emergency software update released on September 25, with XRPL saying it found no evidence of exploitation on any public network.</p>
<h2 id="xrpld-3-4-1-added-overflow-checks-before-disclosure">xrpld 3.4.1 added overflow checks before disclosure</h2>
<p>XRPL released <a href="https://xrpl.org/blog/2026/xrpld-3.4.1" rel="noopener noreferrer nofollow">xrpld 3.4.1</a> as an emergency security update on September 25. The release added overflow checks to payment calculations and strengthened the ledger’s “no-XRP-created” invariant, the control intended to ensure transactions cannot generate XRP.</p>
<p>The network publicly detailed the underlying flaw two weeks later. In its <a href="https://xrpl.org/blog/2026/vulnerabilitydisclosurereport-bug-20261009" rel="noopener noreferrer nofollow">October 9 disclosure</a>, XRPL said the integer overflow affected the payment engine and could have produced spendable XRP beyond the intended cap.</p>
<h2 id="how-crafted-offers-could-have-bypassed-the-invariant">How crafted offers could have bypassed the invariant</h2>
<p>The issue was not described as a simple one-transaction exploit. According to XRPL, an attacker would have needed hundreds of deliberately priced offers, followed by a single payment, to trigger the vulnerable calculation.</p>
<p>That sequence could have bypassed the protection against XRP creation, potentially allowing spendable XRP to be created above the ledger’s designed <a href="https://cryptodaily.co.uk/glossary/grasping-the-significance-of-cryptocurrency-total-supply-limits" rel="noopener noreferrer nofollow">supply limit</a> rather than producing merely an erroneous display or accounting result.</p>
<h2 id="no-public-network-exploitation-found">No public-network exploitation found</h2>
<p>Although XRPL said it found no evidence that the vulnerability had been exploited on a public network, the network’s stated assessment does not change the severity of the flaw described in the disclosure.</p>
<p><a href="https://news.bitcoin.com/featured/xrp-ledger-bug-minted-xrp-overflow/" rel="noopener noreferrer nofollow">Bitcoin.com News</a>, reporting on October 10, characterized the vulnerability as a decade-old issue that could have enabled XRP creation beyond the network’s 100-billion-token cap. Its report also noted that the patch had been deployed before the vulnerability was publicly disclosed.</p>
<p>Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.</p>

XRP Ledger Discloses and Patches Bug That Could Have Broken Its Supply Cap

Table of Contents

Crypto Daily™

Other articles published on Oct 11, 2026

Join our free newsletter for daily crypto updates!