Fehler im XRP Ledger wirft Fragen zur Sicherheit des Angebots auf

CryptoNewsLand · 2026-10-12T19:33:05.000Z

Die Entwickler des XRP Ledger haben einen Fehler aus dem Jahr 2015 behoben, der unter bestimmten Transaktionsbedingungen die Erstellung nicht autorisierter XRP ermöglicht hätte. Berichten zufolge fanden Ermittler keine Hinweise auf eine Ausnutzung des Fehlers in öffentlichen Netzwerken. Tests bestätigten jedoch, dass die Schwachstelle dazu führen könnte, dass XRP ausgegeben werden kann. Das dringende Software-Update behob ein potenzielles Risiko für die Integrität des Angebots und erforderte eine netzwerkweite Koordination der Validatoren bei der Aktualisierung. Die Sicherheit des XRP Ledger rückte in den Fokus, als Entwickler einen alten Softwarefehler behoben, der die Erstellung nicht autorisierter Token ermöglicht hätte.

XRP Ledger's developers fixed a 2015 bug that could have allowed for the creation of unauthorized XRPs under certain transaction conditions.
Investigators reportedly discovered no evidence of exploitation on public networks but testing confirmed the flaw could result in spendable XRP. 
The emergency software update addressed a potential supply-integrity risk and required validators to coordinate upgrades across the network.
The security of XRP Ledger came to the fore when developers fixed an old software bug that could have allowed the creation of unauthorized tokens. 
XRP Ledger Developers Address a Longstanding Vulnerability
RippleX revealed a software vulnerability that dates back to 2015. In some scenarios, an attacker could have created spendable XRP using a vulnerability. The disclosure described a potential security failure, not a confirmed attack.
Whale Insider brought the development to wider attention through a recent post. Its message focused on the possibility of billions of XRP being created without legitimate backing. However, the reported vulnerability was fixed, and investigators found no evidence of public-network exploitation.
 https://twitter.com/WhaleInsider/status/2108781536338145677?s=20
The flaw involved integer overflow within the ledger’s payment engine. During certain transactions, calculations could produce an incorrect amount owed. That error could allow an attacker to receive more XRP than the transaction justified.
The vulnerability required carefully constructed payments involving numerous order-book offers. An attacker could manipulate offer values to trigger the calculation error. Ordinary transactions were not described as routinely activating the flaw.
The Flaw Could Have Threatened XRP Supply Integrity
The concern extended beyond payment accuracy to the ledger’s supply safeguards. Those controls are designed to preserve the protocol’s accounting rules. If calculations failed, unauthorized balances might escape normal validation checks.
According to the disclosure, the same arithmetic problem could affect supply-invariant checks. This raised the possibility that safeguards would fail to identify incorrectly created tokens. Controlled testing reportedly confirmed that the resulting XRP could subsequently be spent.
That detail made the vulnerability more serious than a temporary display or accounting discrepancy. Spendable tokens could potentially circulate as though they were legitimate balances. Such an outcome could undermine confidence in the ledger’s supply integrity.
XRP has a capped total supply of 100 billion. The unauthorized creation may have caused concerns regarding balances and the integrity of supply accounting. The disclosure didn't prove any additional XRP was sold.
Emergency Patch Targets the Security Risk
The vulnerability was reportedly submitted through the XRP Ledger bug bounty process on September 22, 2026. Developers investigated the issue and reproduced it under controlled conditions. The fix appeared in XRPOLD version 3.4.1, released on September 25.
The severity prompted an urgent response from network operators.In addition to the usual amendment procedure, operators were encouraged to upgrade in a timely fashion. According to the disclosure, over 80% of the validators in the default Unique Node List were upgraded on release day.
Coordinating validators is important since the network depends on independent validators that operate with compatible software. A serious flaw can remain relevant until sufficient participants install the correction. Clear disclosures and rapid updates therefore form important parts of blockchain security maintenance.
The report also distinguishes a possible attack from a confirmed incident. According to RippleX, they did not see evidence of the flaw being exploited on public networks. The information available thus indicates that the flaw was fixed without any known public-network attack.
For XRP holders, the key development is the repair of a vulnerability that could have threatened supply rules. The disclosure does not prove that billions of tokens were minted. Instead, it documents a potential exploit, its technical correction, and the reported absence of public exploitation.