# Aztec Says a Soundness Flaw in Its Proving System Puts Funds on Its Live Privacy Network at Risk

Core contributors found the defect on 27 July through internal artificial-intelligence-assisted review and say they cannot determine whether anyone exploited it first.

- Published: 2026-08-25T05:50:40.344Z
- Canonical: https://polylog.news/crypto/2026-08-25/aztec-says-a-soundness-flaw-in-its-proving-system-puts-funds
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [Aztec Network (disclosure)](https://aztec.network/blog/alpha-v5-proving-system-vulnerability), [Aztec Network (Alpha V5)](https://aztec.network/alpha-v5), [Aztec Network (applications)](https://aztec.network/blog/dark-forest-aztec-game-goes-live)

Aztec, the privacy-focused layer-2 network built on Ethereum, [disclosed a critical vulnerability in the proving system](https://aztec.network/blog/alpha-v5-proving-system-vulnerability) behind its Alpha V5 release. According to the disclosure, an attacker may be able to construct a proof that passes verification for a transaction the network should reject, producing a state change outside the rules the protocol is meant to enforce. Contributors identified the flaw on 27 July using internal review assisted by artificial intelligence, and they say they cannot determine whether anyone exploited it before the finding.

This is a soundness defect, not a smart-contract bug, and that distinction decides who can catch it. On a transparent chain, validators re-execute transactions and can detect an invalid state change. On a privacy network, where transaction contents are hidden and the proof is the only evidence the rules were followed, re-execution offers no fallback. Aztec told users to treat funds and applications on [Alpha V5](https://aztec.network/alpha-v5) as exposed to a protocol-level failure until incident response finishes and network operators carry out required actions. Alpha V5 went live on Ethereum mainnet in July with private transaction proving that Aztec says runs more than twice as fast as its predecessor, and [applications have been deploying on it](https://aztec.network/blog/dark-forest-aztec-game-goes-live) since.

It is the second critical proving-system flaw Aztec has disclosed this year. A comparable defect in Alpha V4 surfaced in March, and [users were told to withdraw before 25 June](https://thedefiant.io/news/defi/aztec-v4-withdraw-june-25-v5-upgrade-security-vulnerability) ahead of the V5 upgrade. Aztec says internal and external human audits are now complete, that reviewers have not identified other high-severity or critical Alpha V5 issues at this time, and that a security roadmap covering the remaining work will follow.

The pattern matters more than any single bug. Zero-knowledge (ZK) proving stacks are large, new, and understood in depth by a small number of engineers, and the "Alpha" label Aztec applies is an explicit statement that the network is in the period for finding faults before production. Users who bridged real value into the network carried production risk on pre-production software all the same.

## What this means

Privacy rollups concentrate their entire security assumption in one cryptographic system, and no committee of validators can independently check it. That makes the small teams writing proving code a single point of failure for every asset and application on the network, and it pushes serious users toward chains with multiple independent provers or working escape hatches. Institutions evaluating confidential settlement now have a second data point in five months showing that proof soundness, rather than contract logic, is the live failure surface.

## What to watch

- Whether Aztec's promised security roadmap sets a firm date and whether operators are asked to force withdrawals, which would show the fix requires breaking network continuity rather than a routine upgrade.
- Whether other zero-knowledge rollups respond by adding a second independent prover or a permissionless exit path, the two mechanisms that limit damage when a single proving system fails.
- Whether application teams pause deployments on Aztec, which would indicate builders price proving-system risk higher than the privacy advantage the network offers.