Why did Ripple release an emergency update to the XRP Ledger software in September 2026?

The full answer

What was released on September 25, 2026?

The XRPL.org blog posted “Introducing XRP Ledger version 3.4.1” on September 25, 2026. It states that version 3.4.1 of xrpld, the reference server implementation of the XRP Ledger protocol, is now available [1]. The same post calls it an emergency release to fix security-sensitive issues in the XRPL protocol [1].

Why was it called an emergency release?

The announcement gives one reason: it fixes security-sensitive issues in the protocol [1]. It describes the issues in those words only. No public detail on the specific flaws appears in the announcement as listed on the blog index.

A September 29, 2026 report from cryptonews.net, summarising the XRPL Foundation release notice, says the update adds an amendment named fixBatchV1_2. It also says the notice asks servers to upgrade promptly [2]. The same report says the amendment was expected to enable on October 9 if supermajority support persists [2].

How does it relate to the earlier 3.4.0 release?

Version 3.4.0 of xrpld came out on September 16, 2026 [4]. The 3.4.1 release followed nine days later. The earlier release is covered on the page about what is new in version 3.3.0 in its predecessor and on the version 3.4.0 page. Lending status is covered separately in whether native lending is live.

Is this the first emergency release this year?

No. Cryptonomist reported that an emergency software release, rippled 3.1.1, was issued on February 23, 2026 [3]. The February event involved the Batch amendment, which the separate page on the Batch amendment vulnerability explains. The wider record of halts and incidents is on the outages and incidents page.

What does an amendment do, and who decides?

An amendment changes the ledger’s rules. Validators vote on amendments, and the process is explained in how amendments are approved. The XRPL Foundation’s release notice, as reported by cryptonews.net on September 29, 2026, said fixBatchV1_2 was expected to enable on October 9 if supermajority support persisted, but that is a stated expectation, not a result [2].

What is the case against reading this as a minor event?

Critics of any emergency fix can point out that withholding details leaves outsiders unable to check how serious the flaw was. The XRPL.org announcement labels the issues “security-sensitive” and says no more [1]. The security design that the ledger relies on is covered in how XRP is kept secure without mining. Software changes of this kind do not alter XRP’s fixed supply, which is covered in how many XRP exist. The software’s maintainers are discussed in who funds XRP Ledger software.