The XRP Ledger Foundation has rolled out a critical software update, version 3.2.1, to address a newly discovered vulnerability in how network nodes handle validator manifests. The fix introduces four protective measures that prevent malicious actors from overwhelming nodes with excessive validator data, without affecting the blockchain's normal transaction processing.
The vulnerability, revealed on July 31, 2026, allowed nodes to accept, store, and rebroadcast an unlimited number of manifests from unknown validator keys. This could force nodes to consume unnecessary resources, though it never disrupted ledger closures or consensus. The foundation confirmed that transaction validation remained fully operational throughout the incident, and the priority was to release safeguards before publishing a detailed technical post-mortem.
With version 3.2.1, nodes now reject oversized manifests and limit the number of incoming manifest batches. A cap is placed on bulk manifest data exchanged during peer synchronization, reducing bandwidth abuse. Crucially, each node can only store manifests from a maximum of 100 unknown validator keys, and any such data is automatically discarded during node restarts, preventing persistent storage of unwanted records.
The update separates a focused security repair from broader protocol changes planned for version 3.3.0. That upcoming release, still in development, includes features like BatchV1_1 with corrected inner-signature validation and under-development confidential transfers and sponsored fees. For now, the 3.2.1 upgrade immediately strengthens node resilience and reduces the attack surface, ensuring that the XRP Ledger remains robust against similar manifest flood attempts.
