# Aztec Discloses Soundness Flaw That Could Let a Forged Proof Pass Verification

The privacy network says a crafted proof could validate a transaction the chain should reject, putting funds, applications and contract state on its Alpha V5 network at risk.

- Published: 2026-09-18T05:52:43.927Z
- Canonical: https://polylog.news/crypto/2026-09-18/aztec-discloses-soundness-flaw-that-could-let-a-forged-proof
- 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 (apps live)](https://aztec.network/blog/dark-forest-aztec-game-goes-live)

Aztec, the layer-2 network built for private smart contracts on Ethereum, has disclosed a critical vulnerability in the proving system behind its [Alpha V5 network](https://aztec.network/alpha-v5). According to the [network's disclosure](https://aztec.network/blog/alpha-v5-proving-system-vulnerability), an attacker may be able to construct a proof that passes verification for a transaction the network should reject. Contributors say funds, applications and contract state on V5 should be treated as exposed until incident response finishes. The flaw was found through internal auditing assisted by artificial intelligence, after internal and external human audits had already completed.

A soundness defect is a different class of failure from a smart-contract bug, and the difference is what makes it serious. In a validity rollup, the proof is the authority. If the verifier accepts an invalid state transition, every downstream check that trusts the proof inherits the error, and the usual fallback of re-executing transactions to detect a bad block does not help, because the chain's own rules say the proof was valid. Audits scoped to application code cannot see this surface at all.

This is the second consecutive Aztec release cycle with a proving-system disclosure. The team previously reported a critical vulnerability in Alpha V4 that it said affected the proving system as a whole and could lead to protocol disruption and theft of user funds, and it withheld the technical details until V5 shipped. Embargoed disclosure timed to an upgrade is now a standard pattern for zero-knowledge teams, and it forces users to weigh the cost of staying on a network with a known unpatched class of bug against the cost of exiting.

The exposure is not theoretical, because applications are live. Aztec has been onboarding consumer software and games onto the network, including [a private-state version of Dark Forest](https://aztec.network/blog/dark-forest-aztec-game-goes-live), and the whole design premise of the chain is that balances and contract state stay hidden. Privacy raises the cost of incident response. On a transparent chain, observers can measure a drain in real time. On a shielded one, the people best placed to see an exploit are the attacker and the operator.

Both sides of the artificial-intelligence security argument appear in the same incident. Machine-assisted review caught a defect that human auditors missed, which supports the claim that these tools strengthen defense. It also demonstrates that production zero-knowledge systems contain findable soundness bugs, which is exactly what the other side of that argument warns about.

## What this means

Every validity rollup that relies on a single proving system carries the same structural exposure: one verifier bug can invalidate the chain's entire security claim, and node operators cannot detect it by re-executing blocks. That pushes value toward networks with proof-system diversity, independent verifier implementations and working escape hatches, and it raises the insurance and due-diligence cost for institutions considering confidential on-chain settlement. Privacy chains carry the sharper version of the problem, because the shielded state that is their product also delays detection of a loss.

## What to watch

- Whether Aztec publishes the technical root cause and a fixed release, and how long users are asked to hold funds on a network with a known proving flaw.
- Whether other zero-knowledge teams disclose comparable verifier defects in the coming weeks, which would mark this as a recurring risk class rather than one team's engineering error.
- How much of Aztec's live application activity leaves the network during incident response, as a measure of whether users price soundness risk at all.