Morning Edition · Thursday, October 22, 2026Published at 1:48 AM EDT · New York
Core contributors found the soundness bug on July 27 through AI-assisted internal auditing. The fix will ship only with Aztec's next version, V6, and the team is telling users to treat V5 funds as exposed to a protocol-level failure until then.

Aztec, the privacy-focused Ethereum layer-2 network, disclosed a critical vulnerability in the proving system of its Alpha V5 network. According to Aztec, an attacker could construct a proof that passes verification for a transaction the network should reject. If the network accepted that proof, it would apply a state change outside the rules V5 is meant to enforce. In practice that could mean balances or contract state that no legitimate transaction produced.
Core contributors found the flaw on July 27, 2026, through internal AI-assisted auditing, Aztec said. The disclosure arrives about three months later, and the fix is scheduled for V6. Aztec says it cannot determine whether the flaw was exploited before its contributors found it. The affected system does not record enough information to distinguish ordinary accepted transactions from transactions accepted through the flawed proving path. As a result, historical chain activity cannot show whether exploitation occurred or how large it was. Reviewers have found no other high-severity or critical V5 issues so far. Aztec nevertheless tells users to treat V5 funds, applications and contract state as exposed to a protocol-level failure until incident response is complete and operators take the required network actions.
This is not Aztec's first such disclosure. The team previously published a critical vulnerability in Alpha V4, and it has raised its total bug bounty to $2 million. The Alpha label is the team's stated defense. In its framing, testing networks exist to surface this kind of finding before mainnet.
The structural point concerns privacy rollups in particular. On a transparent rollup, a validator or watcher can re-execute public transactions and notice that a state transition is wrong. On a privacy network, the private inputs never reach validators, so the validity proof is the only check that a transaction followed the rules. When that proof system is unsound, no independent party can audit the damage afterward. Aztec's statement that it cannot quantify any impact follows directly from that design.
What this means
The exposure falls on anyone holding value or deploying applications on privacy layer-2 networks. It also falls on the institutional pitch for confidential execution, which assumes the proof system is the trust anchor. Aztec's response follows the pattern in the tracked thesis: an embargoed fix tied to a version upgrade, and an admission that the bug cannot be detected after the fact. Most users and investors still price these networks mainly on smart-contract audit quality. The consensus view may be underweighting proof-system soundness, which ordinary audits do not cover. AI-assisted auditing found this bug, which supports the argument that the same tools that threaten security also speed up defense. The desk's read is that, within months, privacy networks will face pressure to add a second independent proof system, or an exit mechanism users can trigger without an operator, before they hold meaningful institutional balances. Aztec will likely tie its mainnet timeline to that work. A clean third-party audit of the V6 proving system, combined with no further critical findings through V6, would weaken that read.
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 · Aztec Network
Comments
0No comments yet.