Why Are Zero-Confirmation Transactions Considered Less Secure than Confirmed Transactions?

Zero-confirmation transactions are those that have been broadcast to the network but not yet included in a block. They are vulnerable to double-spending attempts, especially via RBF, because they are not yet secured by the network's consensus mechanism.

A malicious user can replace the unconfirmed transaction with a conflicting one before a miner includes the original.

How Do Zero-Confirmation Transactions Increase the Risk of a Double-Spend?
What Are the Fee-Bumping Rules (E.g. Minimum Fee Increase) for a BIP125 RBF Replacement?
What Is a “Double-Spend” in the Context of a 51% Attack?
What Is ‘Double-Spending’ and Why Is It the Main Concern of a 51% Attack?
How Does the Concept of “Double-Spending” Differ from RBF?
What Is ‘Double-Spending’?
How Does a Transaction’s Confirmation Status Relate to Double-Spending Risk?
How Do Centralized Exchanges Prevent Double-Spending before Blockchain Confirmation?

Glossar