Morning Edition · Tuesday, October 13, 2026Published at 1:42 AM EDT · New York
Contributors found the bug with AI-assisted auditing on July 27, and they say chain history cannot show whether anyone used it. The fix is scheduled for V6.

Aztec, a privacy-focused layer-2 network on Ethereum, disclosed a critical vulnerability in the proving system of its Alpha V5 network. Contributors say they found the flaw on July 27 through internal AI-assisted auditing. 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 in ways V5's rules are meant to forbid.
Aztec told users to treat V5 funds, applications and contract state as exposed to a protocol-level failure. That warning stands until contributors finish their incident response and node operators carry out the required network actions. Aztec also said it cannot tell whether anyone exploited the flaw. The system does not keep the information that would separate a properly accepted transaction from one accepted through the flawed path. Chain history therefore cannot show whether exploitation happened or how much was taken. The fix is planned for V6, with circuit changes that stop the network from accepting proofs tied to the affected proving system.
The flaw is hard to detect because of how Aztec works. On a transparent rollup, an outside observer can re-run transactions and catch an invalid state change. On Aztec, private functions run on the user's own device, and the network receives only a zero-knowledge proof and encrypted commitments. If a false proof verifies, observers have nothing to re-check. The disclosure was published well after the July discovery and tied to the next release. That timing follows the usual practice of keeping a bug private until a fix ships.
This is not the network's first proof-layer incident. Aztec previously published a critical vulnerability in Alpha v4. Meanwhile, the project keeps building its user base. It has launched an onchain version of the Dark Forest game and published an explainer on how gas works on the network.
What this means
A soundness bug lets the network accept a proof of something false. On a privacy rollup, neither validators nor outside observers can detect that afterward, because the data they would need to check is hidden by design. The exposure falls on anyone holding bridged assets or running applications on Aztec V5, and on the wider pitch that institutions can trust privacy networks with confidential activity. Two consecutive alpha releases have now carried critical proof-layer defects. Each was found internally and disclosed together with a planned upgrade, which suggests the codebase is still being hardened rather than finished. The desk expects privacy rollups to respond within months by running several independent proof systems in parallel, adding emergency exit paths for users, and putting tighter limits on deposits. That depends on whether V6 ships with independent proof checks or formal verification of the affected circuits. A V6 that only patches this one bug, followed by a third critical disclosure, would show the risk is ongoing. Institutional adoption of confidential execution would then be delayed rather than accelerated.
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 (vulnerability disclosure) · Aztec Network (Alpha V5) · Aztec Network (Dark Forest) · Aztec Network (gas) · Aztec Network (Alpha v4 disclosure)
Comments
0No comments yet.