Vulnerabilitydisclosurereport Bug Feb2026

This vulnerability disclosure report contains technical details of the XRPL Batch amendment bug reported on February 19, 2026.

Date Reported: February 19, 2026

Affected Version(s): rippled 3.1.0 (with the Batch amendment enabled)

On February 19, 2026, Pranamya Keshkamat and Cantina AI identified a critical logic flaw in the signature-validation logic of the XRPL Batch amendment. The bug allowed an attacker to execute inner transactions on behalf of arbitrary victim accounts without their private keys, enabling unauthorized fund transfers and ledger state changes. The amendment was in its voting phase and had not been activated on mainnet; no funds were at risk. Note that even before this bug was reported, the Batch amendment was disabled due to extra caution around ensuring the fixBatchInnerSigs amendment activated first.

UNL validators were immediately advised to vote "No" on the amendment. The emergency release rippled 3.1.1 marks both Batch and fixBatchInnerSigs as unsupported, preventing activation. A corrected replacement, BatchV1_1 , has been implemented and is currently under review; no release date has been set.

If the Batch amendment had activated before this bug was caught, an attacker could have:

Pranamya Keshkamat and the autonomous AI security tool Apex (developed by Cantina AI ) identified the vulnerability via static analysis of the rippled codebase and submitted a responsible disclosure report. Ripple engineering teams promptly validated the report with an independent proof-of-concept and a full unit-test reproduction. Remediation began the same evening.

When the Batch amendment is enabled, inner transactions in a batch are intentionally unsigned; authorization is delegated entirely to the outer batch's list of batch signers. The function responsible for validating those signers contained a critical loop error: when it encountered a signer whose account did not yet exist on the ledger and whose signing key matched their own account (the normal case for a brand-new account), it immediately declared success and exited, skipping validation of all remaining signers entirely.

Expected post-fix behavior:

rippled 3.1.1 is available now. The corrected BatchV1_1 amendment will be included in a future release following completion of its review; no date has been set.

Thanks to Pranamya Keshkamat and Cantina AI (whose autonomous security tool Apex identified the vulnerability) for responsible and thorough disclosure. Their detailed bug report, proof-of-concept, and constructive collaboration throughout the remediation process were invaluable.

Thanks also to the UNL validators who moved swiftly to vote against the affected amendment, the Ripple and XRPL Foundation engineering teams for the expedited review and emergency release, and the broader community of validators, developers, and contributors who keep the XRP Ledger safe and secure.

To report security issues, [email protected] .