Morning Edition · Saturday, September 19, 2026Published at 1:45 AM EDT · New York
Contributors say an attacker could build a proof that verifies for a transaction the network should reject, and the fix waits for the V6 release.

Aztec, the privacy-focused Ethereum layer-2 network, has disclosed a critical vulnerability in the proving system behind its Alpha V5 release. According to the project's disclosure, an attacker could construct a proof that passes verification for a transaction the network is supposed to reject, and an accepted proof of that kind would move the chain into a state its own rules forbid. Contributors say they found the flaw through internal auditing assisted by artificial intelligence, that they cannot determine whether anyone exploited it beforehand, and that users should treat funds, applications and contract state on V5 as exposed until operators complete the required network actions. The fix is scheduled for the V6 release, including circuit changes that stop the network accepting proofs tied to the affected system.
This is a different failure class from a smart-contract exploit. On an optimistic rollup, honest validators re-execute transactions and can catch an invalid state transition. A zero-knowledge system replaces re-execution with a mathematical argument, so if the argument itself is unsound, there is no additional check inside the protocol to catch the error. On a privacy network the gap is wider, because the data needed to independently check balances is encrypted by design. Soundness is not one control among several. It is the control.
The disclosure pattern is now familiar. Aztec published a comparable critical vulnerability notice for Alpha v4 and has raised its bug bounty to $2 million. Two critical proving bugs surfacing in consecutive alpha releases are evidence that the review process is working as intended on pre-mainnet software, and also that proving stacks are shipping faster than anyone can fully verify them.
What this means
Every rollup that settles on Ethereum with validity proofs carries this risk class, and the users exposed are the ones who cannot audit the circuits themselves. Two outcomes are possible. Either teams normalise embargoed disclosure paired with a scheduled upgrade, in which case proof-system diversity and working fallback mechanisms become the features institutions ask about first, or a soundness bug reaches a network holding significant value before a fix ships, and the losses land on depositors with no recovery path because the invalid state was accepted as valid. Aztec catching this on alpha software rather than on mainnet is the distinction that matters.
Part of a tracked trend
Proving-System Bugs Become a Distinct Rollup Risk
Soundness defects in zero-knowledge proving systems will keep surfacing as a risk class separate from smart-contract exploits, because validator re-execution — the fallback most rollups rely on — cannot catch them, forcing teams into embargoed disclosure timed to upgrades and pushing users toward proof-system diversity and escape hatches.
Start a discussion in Townsquare.
More from this edition
What to watch
Observations to monitor, not financial advice.
Synthesized from: Aztec Network · Aztec Network (Alpha V5)
Comments
0No comments yet.