Morning Edition · Thursday, August 13, 2026Published at 1:53 AM EDT · New York
Core contributors found the defect on 27 July through internal artificial-intelligence-assisted auditing, and say funds, applications and contract state on the V5 alpha network are exposed.

Aztec, the privacy-focused layer-2 network on Ethereum that runs private smart contracts, disclosed a critical vulnerability in the proving system behind its Alpha V5 release. Contributors identified the defect on 27 July through internal auditing assisted by artificial-intelligence tooling. Aztec states that an attacker may be able to construct a proof that passes verification for a transaction the network should reject, and that funds, applications and contract state on V5 should be treated as exposed until incident response finishes and operators complete the required network actions.
This is a soundness failure, not a bug in an application contract. A zero-knowledge rollup replaces re-execution with a mathematical proof, so if the verifier can be convinced by an invalid proof, the protocol has no additional check behind it. Validators cannot catch the problem by re-running transactions, because the design deliberately removed that step. That is what separates proving-system defects from ordinary smart-contract exploits and why teams disclose them on a schedule tied to upgrades rather than immediately.
It is also the second such disclosure in the same code lineage this year. Aztec previously told V4 users to withdraw ahead of a June deadline after a critical flaw the team said affected the proving system as a whole. V5, released with roughly halved private-transaction proving costs, remains labeled alpha software, and Aztec has said this is the phase in which findings of this kind surface. No exploitation has been reported.
Aztec, which converts a severe defect into evidence that its internal auditing works, and competing zero-knowledge rollups that can point to a rival's soundness failure while their own verifiers go unaudited by outsiders.
Part of a tracked trend
Proving-System Bugs Become a Distinct Rollup Risk
Soundness defects in zero-knowledge proving systems will keep surfacing as a risk class separate from smart-contract exploits, because validator re-execution — the fallback most rollups rely on — cannot catch them, forcing teams into embargoed disclosure timed to upgrades and pushing users toward proof-system diversity and escape hatches.
Start a discussion in Townsquare.
More from this edition
The entire account rests on Aztec's own disclosure with no independent confirmation of severity, and the team's stated position is stronger than "no exploitation reported": it says the system cannot distinguish transactions accepted through the flawed path from ordinary ones, so exploitation can be neither ruled out nor quantified.
An open-source-intelligence read of how likely this story is true with its real nuance, not a judgment of any outlet. It assesses the claim, weighing independent and adversarial reporting. How we label confidence.
What this means
Every zero-knowledge rollup asks users to trust a verifier contract and the circuits behind it, and a soundness bug converts that trust into an unbacked claim on the bridge holding the deposits. The exposed parties are depositors on the privacy network and any application settling through it. Two paths follow from here. Contributors ship fixes and the disclosure becomes evidence that pre-mainnet auditing works, or a similar defect surfaces after real capital arrives, which would push serious users toward multiple independent proof systems and emergency withdrawal mechanisms rather than a single prover.
What to watch
Observations to monitor, not financial advice.
Synthesized from: Aztec Network · Aztec Network (Alpha V5) · The Defiant
Comments
1Aug 13, 2:00 PM · edited
A soundness failure in a ZK system means the one guarantee that replaces trust in the prover is gone, so exposure on V5 alpha is total, not bounded by which contracts have access controls.