# Aztec Discloses a Critical Flaw in the Proving System Behind Its Live Privacy Network

Contributors said internal review assisted by artificial intelligence found on July 27 that an attacker could construct a proof that verifies a transaction the network should reject, six days after the V5 mainnet alpha went live.

- Published: 2026-08-15T05:40:49.580Z
- Canonical: https://polylog.news/crypto/2026-08-15/aztec-discloses-a-critical-flaw-in-the-proving-system-behind
- 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), [Crypto Briefing](https://cryptobriefing.com/aztec-v5-private-execution-ethereum-l2/), [The Defiant](https://thedefiant.io/news/defi/aztec-v4-withdraw-june-25-v5-upgrade-security-vulnerability)

Aztec, the privacy-focused Ethereum layer-2 network, has disclosed a [critical vulnerability in the proving system](https://aztec.network/blog/alpha-v5-proving-system-vulnerability) of its Alpha V5 network. Core contributors identified the flaw on July 27 through internal auditing assisted by artificial intelligence. According to the disclosure, an attacker could build a proof that passes verification for a transaction the network should have rejected. Reviewers have not identified other high-severity or critical issues in V5 at this time, and internal and external human audits have completed while machine-assisted review continues.

The timing is uncomfortable. [Alpha V5 launched](https://cryptobriefing.com/aztec-v5-private-execution-ethereum-l2/) on July 21 after a governance vote, bringing a fully private execution environment and roughly halved proving costs. The flaw was found six days later.

This is the second consecutive version to carry a proving-system defect. Aztec found a critical bug in Alpha V4 in March, and under its transparency commitments it disclosed the details when the V5 upgrade proposal went on-chain, [telling V4 users to withdraw](https://thedefiant.io/news/defi/aztec-v4-withdraw-june-25-v5-upgrade-security-vulnerability) before the late-June cutoff. Of that earlier bug the team wrote that it affected the proving system as a whole and was not mitigated by public re-execution by the committee of validators.

That finding is the important one, and it applies beyond Aztec. Most rollups treat validator re-execution as the backstop that catches a bad state transition. A soundness defect in the proof system itself defeats that backstop, because the fraudulent transition arrives with a proof the verifier accepts. It is a distinct risk from a smart-contract exploit, it cannot be found by auditing application code, and it forces teams into embargoed disclosure timed to an upgrade rather than an immediate public warning.

The evidence here supports two readings at once. Aztec is running an explicitly labeled alpha, it is publishing what it finds, and machine-assisted review is surfacing defects that human audits missed. Against that, users hold funds on a live network whose security depends on a component that has now failed review twice, and the [product surface keeps expanding](https://aztec.network/alpha-v5) while the proving stack is still under repair.

## What this means

Proof-system soundness is the single assumption that a zero-knowledge rollup cannot delegate to anyone else, and Aztec has now found defects in it in two consecutive releases. Users of privacy layer-2 networks are exposed in a way they cannot inspect, because a forged proof looks identical to a valid one from the outside. The beneficiaries of repeated disclosures are teams selling proof-system diversity, formal verification and escape mechanisms that let users exit without trusting the prover, and the losers are rollups whose only defense is a validator set that re-executes transactions it cannot see.

## What to watch

- Whether Aztec publishes the promised security roadmap and a V6 release path, which would show whether the fix is a patch or a redesign of the proving stack.
- Whether other zero-knowledge rollups disclose comparable soundness bugs found through machine-assisted review, since a cluster of disclosures would mean the defects were always there rather than newly introduced.
- Deposit and withdrawal flows on Aztec after the disclosure, which measure whether users price proving-system risk or ignore it.