Morning Edition · Wednesday, October 7, 2026Published at 1:31 AM EDT · New York
Core contributors found the bug on July 27 using AI-assisted auditing. They say they cannot tell whether anyone exploited it, so funds and contract state on V5 should be treated as exposed until a fix ships in V6.

Aztec, the privacy-focused Ethereum layer-2 network, has disclosed a critical vulnerability in the proving system of its Alpha V5 network. The proving system is the component that checks cryptographic proofs that a transaction is valid. An attacker could build a proof that passes verification for a transaction the network should reject. If the network accepted such a transaction, it could change state (the record of balances and contract data) outside the rules that V5 is meant to enforce.
Core contributors found the flaw on July 27, 2026, through internal AI-assisted auditing. The disclosure came weeks later. Aztec says it cannot determine whether anyone exploited the flaw before it was found. The affected system does not record enough information to tell normal transactions apart from transactions accepted through the flawed proving path. The team says V5 funds, applications and contract state should be treated as exposed to a protocol-level failure until incident response is complete and operators carry out the required network actions.
The fix will come in V6. That release will include circuit updates (changes to the proof-system circuits) that stop the network from accepting proofs tied to an affected proving system. L2BEAT's project page now lists the known critical proving-system vulnerability as a risk to funds.
This is not the first such disclosure on Aztec's alpha network. The team previously published a critical vulnerability in Alpha V4. A soundness bug (one that lets invalid proofs pass as valid) differs from an ordinary smart-contract exploit. In a validity rollup, the verifier is the final check, and validators do not re-execute private transactions they cannot see. On a privacy network, a forged proof could create or move value without any public record that an outside party could audit afterward.
What this means
Privacy rollups ask users to trust a cryptographic verifier instead of public re-execution. A soundness bug therefore cannot be detected after the fact, which is why Aztec cannot rule out past exploitation. The exposed parties are V5 depositors, application teams building on Aztec, and the wider institutional case for confidential execution, which assumes proofs are reliable. Aztec has now found a critical flaw in V4 and again in V5. Disclosure is timed to the next upgrade, and AI-assisted review is finding these bugs before outside attackers do. Few market participants yet recognize that a privacy chain can lose value without any visible trail, which makes the risk hard to price. The likelier outcome over the next several months is that privacy L2s add proof-system diversity, such as multiple provers or trusted-execution checks, along with forced-exit mechanisms (exit routes a user can trigger without the operator) before they seek institutional deposits. That holds provided more audits keep finding soundness flaws. This read is wrong if V6 ships and runs through a sustained period of external audits and bounty claims with no new critical finding.
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 · Aztec Network · L2BEAT
Comments
0No comments yet.