# Aztec Discloses Critical Flaw in the Proving System Behind Its Alpha V5 Privacy Network

Contributors say an attacker could build a proof that verifies for a transaction the network should reject, and the fix is deferred to the next release.

- Published: 2026-09-07T05:46:58.893Z
- Canonical: https://polylog.news/crypto/2026-09-07/aztec-discloses-critical-flaw-in-the-proving-system-behind-i
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [Aztec Network](https://aztec.network/blog/alpha-v5-proving-system-vulnerability), [Aztec Network](https://aztec.network/alpha-v5), [Aztec Network](https://aztec.network/blog/dark-forest-aztec-game-goes-live)

Aztec, the privacy-focused Ethereum layer-2 network, [disclosed a critical vulnerability in the proving system that secures its Alpha V5 release](https://aztec.network/blog/alpha-v5-proving-system-vulnerability). Contributors identified the defect on July 27 through internal auditing assisted by artificial intelligence, and describe an attacker who could construct a proof that passes verification for a transaction the network should reject. Aztec told users to treat funds, applications and contract state on V5 as exposed to a protocol-level failure until incident response finishes and network operators complete the required actions. The repair is planned for the next release rather than a patch to the current one.

The class of bug matters more than the individual instance. A zero-knowledge rollup replaces re-execution with mathematics: the layer-1 contract accepts a state transition because a proof says it is correct. When the proving system itself is unsound, nothing downstream catches the error, because there is no independent party recomputing the result. That is the structural difference from a smart-contract exploit, where honest nodes at least see the transaction that drained the pool.

This is the second such disclosure from the same team inside six months. Aztec published a critical vulnerability in Alpha V4 in March, saying that flaw affected the proving system as a whole and could allow theft of user funds. The V5 release was presented as a substantial upgrade to [the Alpha network](https://aztec.network/alpha-v5), with applications including [a live on-chain game built on private state](https://aztec.network/blog/dark-forest-aztec-game-goes-live). Aztec says internal and external human audits are complete, that reviewers have found no other high-severity or critical V5 issues so far, and that AI-assisted review continues.

The disclosure is evidence for a claim that privacy engineers have made for a while and that most users have not taken into account. Proof systems are young software, the circuits are hard to reason about, and the industry has been shipping them into production faster than it has built independent verification of them. Aztec's decision to publish before the fix ships, rather than after, at least gives users the information needed to withdraw.

## What this means

Rollup users are being asked to trust a cryptographic claim they cannot check, and this class of defect breaks the fallback that most chains rely on, because validators re-executing transactions cannot detect an unsound proof. The exposed parties are depositors on proof-based layer-2 networks and the applications built on them, especially privacy networks where public state is deliberately unavailable for reconstruction. The commercial consequence is that proof-system diversity, escape hatches and formal verification of circuits move from research topics to procurement requirements for anyone deploying real capital on a rollup.

## What to watch

- Whether Aztec's next release ships on schedule and whether the network requires operators to act before users can withdraw, which shows how much practical control the sequencer set still holds.
- Whether other proof-based networks publish reviews of the same circuit component, since a shared library defect would turn one disclosure into an industry-wide patch cycle.
- How much of the bug bounty pipeline is now driven by AI-assisted auditing rather than human review, because that changes how fast defects surface and how often emergency upgrades are needed.