# Aztec Discloses a Critical Proving-System Flaw in Alpha V5 and Says It Cannot Tell Whether Anyone Exploited It

The bug could let an attacker submit a forged proof that the network accepts, and the fix will arrive only with the V6 release.

- Published: 2026-10-20T05:39:30.204Z
- Canonical: https://polylog.news/crypto/2026-10-20/aztec-discloses-a-critical-proving-system-flaw-in-alpha-v5-a
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [Aztec Network (blog)](https://aztec.network/blog/alpha-v5-proving-system-vulnerability), [Aztec Network (Alpha V5)](https://aztec.network/alpha-v5), [Aztec Network (blog)](https://aztec.network/blog/dark-forest-aztec-game-goes-live)

Aztec, a privacy-focused layer-2 network on Ethereum, has [disclosed a critical vulnerability](https://aztec.network/blog/alpha-v5-proving-system-vulnerability) in the proving system behind its [Alpha V5 network](https://aztec.network/alpha-v5). According to the team, an attacker may be able to construct a proof that passes verification for a transaction the network should reject. If the network accepted that proof, the transaction could alter state in ways that break Alpha V5's own rules.

Aztec says the flaw puts Alpha V5 funds, applications and contract state at risk. The team also says it cannot determine whether anyone exploited the bug before its own contributors found it. The system does not record enough information to separate ordinary transactions from transactions accepted through the flawed proving path. As a result, the chain's history cannot show whether an exploit happened or how much damage it caused.

This is a soundness defect, a different class of failure from a smart-contract exploit. In a privacy network, users generate proofs on their own devices, and the network checks only the proof itself. Validators never see the underlying data, so they cannot re-execute a transaction to catch a false proof. Aztec says findings from this incident will shape the upcoming V6 release, which will include circuit updates that stop the network from accepting proofs tied to the affected proving system. Reviewers have found no other high-severity or critical Alpha V5 issues so far.

Aztec has made this kind of disclosure before. It previously published a [critical vulnerability disclosure for Alpha V4](https://aztec.network/blog/critical-vulnerability-in-alpha-v4) and has since [raised its total bug bounty to $2 million](https://aztec.network/blog/aztec-network-raises-total-bug-bounty-to-2-million). The team describes the Alpha network as a testing ground meant to surface exactly these flaws. Developers have already deployed applications there, including an [on-chain version of the Dark Forest game](https://aztec.network/blog/dark-forest-aztec-game-goes-live).

## What this means

Anyone holding value or running applications on Aztec's Alpha network is exposed, and so, more broadly, is every privacy rollup whose security depends on a single proving system. A soundness bug in a shielded system is especially serious, because hidden balances can conceal counterfeit supply. The closest precedent is Zcash. In 2018, its developers found a counterfeiting flaw in the original Sprout parameters, fixed it quietly in the Sapling upgrade, and disclosed it in 2019. They could not prove from the ledger that no one had exploited it. Their fallback was turnstile accounting, which checks total value as funds leave the old pool. Analysts generally treat Alpha-stage bugs as routine. What sets this case apart is Aztec's statement that the chain's history cannot settle whether an exploit occurred. That makes migration accounting the real test of user trust, more than the patch itself. The more likely outcome is that V6 ships with a forced migration and some form of balance check at the boundary within months, while Aztec's timeline toward a production network slips later. If V6 ships without any public reconciliation of total supply, this read is wrong, and users would have only the team's word that balances are intact.

## What to watch

- Whether V6 includes a public check that total balances leaving V5 match total deposits. A mismatch would be the only on-chain evidence that the flaw was exploited.
- Whether other zero-knowledge rollups publish audits of their proving-system soundness or add a second, independent prover. Either step would show the risk class is being priced in across the sector.
- Any change to Aztec's stated schedule for a production network after this disclosure.