What Is a “Re-Entrancy Attack” and Why Is It a Common Smart Contract Vulnerability?

A re-entrancy attack is a critical smart contract vulnerability where an external malicious contract repeatedly calls back into the original vulnerable contract before the original contract has finished updating its state (e.g. updating a balance). This allows the attacker to drain funds multiple times.

It is common because developers often overlook the potential for external calls to hijack the execution flow, making it a frequent target for exploitation.

What Is a Reentrancy Attack in the Context of Smart Contract Vulnerabilities?
Why Must State Updates Occur before External Calls?
What Are the Security Risks Associated with Rebase Token Smart Contracts?
What Is a “Read-Only” Reentrancy Attack?
How Does a Reentrancy Attack Specifically Exploit Smart Contract Logic?
What Is the Risk of a ‘51% Attack’ on a DEX DAO?
What Is a ‘Reentrancy Attack’ and How Does It Exploit Smart Contract Logic?
What Is a Common Pitfall When Implementing Access Control (Checks) in Smart Contracts?

Glossar