XRP Ledger Activates fixCleanup3_4_0 to Patch Token Creation Vulnerability

iconKuCoinFlash
Share
AI summary iconSummary
The XRP Ledger deployed fixCleanup3_4_0 on November 4, 2026, at 22:52 Beijing Time to address a vulnerability related to token destruction permissions. The flaw permitted these permissions to be exploited for creating new tokens, affecting the delegated issuance system. Assets such as stablecoins were impacted, but XRP remained unaffected. No confirmed attacks have been reported. The update was implemented amid continued activity in new token listings on the network.

Odaily Planet Daily reports that, according to XRP Ledger monitoring, the XRP Ledger activated a fix named "fixCleanup3_4_0" at 22:52 Beijing time on November 4, patching a vulnerability: under certain conditions, accounts previously authorized only to destroy issuer tokens could also create new tokens. This vulnerability affected the network’s permissioned delegation system—for example, stablecoin issuers may authorize payment processors to destroy tokens when customers redeem them, without granting them the authority to create new tokens; under the old rules, accounts with limited destruction permissions could potentially mint new tokens. The vulnerability impacted assets issued on the XRP Ledger, including stablecoins, but did not affect XRP itself. No publicly confirmed exploitation cases have been reported to date.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.