# Aztec discloses a critical soundness flaw in its Alpha V5 proving system, with the fix deferred to V6

An attacker could construct a proof that verifies for a transaction the network should reject, and contributors found the defect through internal artificial-intelligence-assisted auditing.

- Published: 2026-09-26T05:50:55.881Z
- Canonical: https://polylog.news/crypto/2026-09-26/aztec-discloses-a-critical-soundness-flaw-in-its-alpha-v5-pr
- 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, has disclosed a [critical vulnerability in the proving system behind its Alpha V5 release](https://aztec.network/blog/alpha-v5-proving-system-vulnerability). Core contributors identified the defect on July 27, 2026 through internal auditing assisted by artificial intelligence tools. The flaw allows an attacker to construct a proof that passes verification for a transaction the network should have rejected, which is a soundness failure rather than a bug in application code.

That distinction determines how serious the flaw is. On a zero-knowledge rollup, the verifier contract accepts state transitions because a proof says they are valid. Validators do not re-execute private transactions to check the result, so this kind of defect cannot be caught by the re-execution check that optimistic rollups depend on. Aztec said funds, applications and contract state on [Alpha V5](https://aztec.network/alpha-v5) should be treated as exposed to a protocol-level failure until contributors finish incident response and network operators complete the required actions. Internal and external human audits have concluded, artificial-intelligence-assisted review continues, and reviewers report no other critical or high-severity findings in V5 at this time. The repair is scheduled for V6.

Aztec has been shipping quickly into this Alpha phase, including a live on-chain version of the [hidden-information game Dark Forest](https://aztec.network/blog/dark-forest-aztec-game-goes-live) built to demonstrate private state. Alpha networks exist precisely so that this class of defect surfaces before real value depends on it. The finding came from the team's own tooling rather than from an external audit. That shows how difficult it is to review a proving system from outside the team that built it.

## What this means

The exposed party is anyone holding balances or deployed contract state on an Alpha network whose safety rests on a single proving stack, and the mechanism is that proof verification substitutes for re-execution, so a defect in the prover becomes a defect in the ledger itself. The precedent is Zcash, which discovered a subversion-of-soundness flaw in its original proving system in 2018, patched it quietly ahead of disclosure, and found no evidence of exploitation. Aztec's handling follows the same pattern of embargo, fix, then publication. The likelier outcome over the coming months is that privacy-focused rollups compete on prover assurance, meaning multiple independent proving implementations, formal verification of circuit constraints, and working escape hatches, rather than on transaction throughput or fee level. What would disprove that read is a repeat soundness disclosure that causes a real loss on a live network, which would push builders toward simpler designs with smaller trusted circuits instead.

## What to watch

- Whether Aztec publishes the constraint-level detail of the V5 flaw when V6 ships, because the crypto-engineering community cannot check for the same pattern in other circuits until it does.
- Whether other zero-knowledge teams respond with independent prover implementations or formal verification commitments, which would show the risk is being treated as structural rather than as one team's mistake.
- How much artificial-intelligence-assisted auditing contributes to future disclosures, since a rising share would change who finds these defects first and on what timeline.