# Aztec Discloses a Second Critical Proving-System Flaw, This Time in Its Live Alpha V5 Privacy Network

Core contributors say an internal audit assisted by artificial intelligence found that an attacker could build a proof the verifier accepts for a transaction the network should reject.

- Published: 2026-08-10T05:51:49.058Z
- Canonical: https://polylog.news/crypto/2026-08-10/aztec-discloses-a-second-critical-proving-system-flaw-this-t
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [Aztec Network](https://aztec.network/blog/alpha-v5-proving-system-vulnerability), [Aztec Network (Alpha V5)](https://aztec.network/alpha-v5), [Aztec Network (gas design)](https://aztec.network/blog/how-gas-works-on-aztec)

Aztec, the Ethereum layer-2 network built for private smart contracts, has told users that its current release carries a protocol-level failure in the component that decides what is true. Contributors identified the flaw on 27 July 2026 through internal auditing assisted by artificial intelligence, and describe it as allowing an attacker to construct a proof that passes verification for a transaction the network should reject. Funds, applications and contract state on V5 should be treated as exposed until incident response finishes.

The distinction matters. This is a soundness failure, not a privacy leak. On a zero-knowledge rollup, the proof is the only thing standing between a valid state transition and an invented one. Aztec has said of this class of bug that it cannot be caught by having validators publicly re-execute transactions, because there is no public execution to re-run. Confidentiality is exactly what removes that backup check.

This is the second such disclosure in five months. Aztec found a critical proving-system vulnerability in Alpha V4 in March, withheld the details, and [urged users to withdraw before 25 June](https://thedefiant.io/news/defi/aztec-v4-withdraw-june-25-v5-upgrade-security-vulnerability) so that the patch and the disclosure could ship together in V5. V5 was the fix. V5 now has its own. The team has been consistent that Alpha is experimental and that users should not deposit more than they are willing to lose, and the network is still pre-mainnet, so the money at risk is small relative to the general-purpose rollups. The reputational risk is significant.

Two readings compete, and the next few weeks decide between them. Either the AI-assisted audit pipeline is working as intended and is clearing a backlog of latent proving bugs faster than attackers can find them, in which case disclosure frequency rises now and falls later. Or the proving stack for private execution is simply not mature enough for value at scale, in which case each release cycle produces another critical finding and mainnet slips again. The evidence that separates them is whether the next disclosure comes from a defender or from a drained contract.

## What this means

Privacy rollups are being marketed as a prerequisite for serious institutional use of public blockchains, and a soundness bug directly undermines that claim, because a private system cannot rely on outside observers re-executing transactions to catch a forged state. The exposed parties are the privacy layer-2 networks competing for the same institutional mandate and the applications that committed to building on them, which now face longer security review before any regulated counterparty deposits size. The offsetting read is that both of Aztec's critical findings came from its own reviewers rather than from an attacker, which is what a functioning disclosure process looks like.

## What to watch

- Whether Aztec publishes the technical detail of the V5 flaw or holds it until the next release, as it did with V4. Repeating the delayed-disclosure pattern tells you the fix is not yet deployed.
- Whether other zero-knowledge stacks that share circuit libraries or the same proving system issue advisories. A shared root cause would turn a single-network problem into an ecosystem one.
- Any movement in Aztec's mainnet timeline. A slip signals that the team judges the proving stack unready for unrestricted deposits.