What vulnerability did XRPL Labs report in the XRP Ledger's Batch Amendment?

The full answer

What did XRPL Labs report?

The XRPL.org blog lists the item under Advisories as “Vulnerability Disclosure Report: XRPL Batch Amendment – Unauthorized Inner Transaction Execution,” by XRPL Labs, dated February 26, 2026 [1]. XRPL Labs reported the vulnerability in the XRPL Batch amendment, described as unauthorized inner transaction execution [1].

The report itself says it contains technical details of a Batch amendment bug reported on February 19, 2026 [2]. Its header lists the affected version as rippled 3.1.0 with the Batch amendment enabled. It says Pranamya Keshkamat and Cantina AI identified a critical logic flaw in the signature-validation logic of the amendment [2].

What is the Batch amendment?

Ripple said in September 2025 that XRPL version 2.5.0, published in June 2025, introduced amendments including Batch Transactions [3]. XRPL.org’s February 26, 2026 disclosure report described a flaw in the signature-validation logic of the Batch amendment that let an attacker execute inner transactions on behalf of arbitrary victim accounts without their private keys.

How did the flaw work?

The report explains the root cause. The XRPL.org advisory said Pranamya Keshkamat and Cantina AI identified a critical logic flaw in the signature-validation logic of the Batch amendment on February 19, 2026, affecting rippled 3.1.0 with Batch enabled. According to the advisory, the bug allowed an attacker to execute inner transactions on behalf of arbitrary victim accounts without their private keys [2]. The advisory said the amendment was in its voting phase and had not been activated on mainnet.

The advisory added that this could enable unauthorized fund transfers and ledger state changes [2].

Was any money lost?

No. XRPL.org said the amendment was in its voting phase and had not been activated on mainnet, and that no funds were at risk [2]. Amendments need validator approval before they take effect, which is covered in how XRP Ledger upgrades get approved.

What was done about it?

Version 3.1.1 of rippled, published February 23, 2026, disabled the Batch and fixBatchInnerSigs amendments because of a severe bug [1]. The advisory says this release marks them as unsupported, which stops them receiving validator votes or being activated on the network [2]. That release came three days before the public report.

What is the case for concern?

The flaw was in code that had already shipped in a released server version, 3.1.0 [2]. An outside party found it, not the pre-release review. The same release line also introduced the Single Asset Vault and Lending Protocol, according to the XRPL.org release notes of January 28, 2026 [1]. For the status of lending see whether native lending is live. For earlier incidents on the ledger see the history of halts, forks and losses.

What is not yet known?

As of October 7, 2026, the XRPL.org advisory and release notes give no date for Batch returning to validator voting.