Briefing
A critical network partition event impacted the Cardano blockchain on November 21, 2025, when a legacy software vulnerability was exploited to split the mainnet into two competing histories. This consensus failure, triggered by a malformed delegation transaction, resulted in significant operational disruption as exchanges and stake pool operators halted services to prevent inconsistencies. While no user funds were compromised, the incident exposed a high-severity flaw allowing an oversized hash to bypass initial validation, demonstrating that foundational protocol-layer vulnerabilities dating back to 2022 remain an active threat vector.
Context
The prevailing security posture for established Proof-of-Stake blockchains often overlooks vulnerabilities residing in legacy code components that govern core protocol logic. This incident leveraged a known class of risk → a systemic design flaw where the system’s input validation was insufficient to handle adversarial or malformed transaction data. The risk factors were heightened by the complexity of maintaining backward compatibility with older transaction types, creating a non-obvious attack surface within the core node software itself.
Analysis
The attack vector was a malformed delegation transaction that contained an oversized hash, which was able to bypass the initial validation checks in the legacy node software. This successful bypass allowed the corrupted transaction to be propagated across the network, leading to a divergence in the block history as different nodes processed the invalid input differently. The immediate chain of effect was a chain split, effectively partitioning the network into two competing versions of the ledger and causing a temporary consensus failure across the entire distributed system. The attack was successful because the bug was a dormant, high-severity logic flaw dating back to 2022 that was only revealed when the specific malformed input was introduced.
Parameters
- Total Funds Lost → $0 (User funds confirmed safe) – The exploit was a network integrity attack, not a financial drain.
- Vulnerability Root Cause → Legacy delegation transaction logic flaw – A bug in the validation process for an oversized hash.
- Immediate Mitigation → Node Software Update 10.5.3 – Required upgrade for all Stake Pool Operators and exchanges to reconcile the chain split.
- Market Reaction → ADA Price Drop – The token fell 3% in the 48 hours following the disclosure due to market anxiety over network stability.
Outlook
Immediate mitigation requires all node operators and exchanges to upgrade to the patched software versions (10.5.2/10.5.3) to restore a unified chain history and resume normal operations. The second-order effect is a renewed focus on deep, protocol-level auditing of all legacy transaction types, especially those with complex validation logic. This incident will likely establish new security best practices mandating formal verification for core consensus components, reinforcing that network resilience is as critical as smart contract security.
