Morning Edition · Friday, September 25, 2026Published at 9:11 AM EDT · New York
Contributors found through internal AI-assisted auditing that an attacker could build a proof that verifies for a transaction the network should reject, with the fix deferred to V6.

Aztec, the privacy-focused layer-2 network on Ethereum, told users that its live Alpha V5 release carries a critical vulnerability in the proving system. Contributors identified the defect on 27 July 2026 through internal auditing assisted by artificial intelligence (AI). The failure is a soundness break: an attacker may be able to construct a proof that passes verification for a transaction the protocol should have rejected. Funds, applications and contract state on V5 should be treated as exposed to a protocol-level failure until operators complete the required network actions, and the corrective release is planned for V6.
This is the second consecutive version of the network to ship with a proving-system flaw disclosed after launch. Aztec disclosed a critical vulnerability in Alpha V4 in March, urged users to withdraw before a governance vote made the details public, and delivered the patch in V5. The team frames these findings as the intended output of an alpha phase, in which the audit process is meant to surface exactly this class of defect before wider deployment.
The disclosure lands while Aztec pushes usage forward. The network has been promoting applications built on private execution, including a live version of the Dark Forest game and documentation on how gas works on Aztec, and it markets V5 as the current Alpha network release.
A soundness bug is a different risk category from a smart-contract exploit. Validator re-execution, the fallback most rollups rely on to catch bad state transitions, cannot detect a proof that verifies correctly against a flawed circuit. The user's real protections are conservative deposit limits, the escape hatch, and the team's willingness to disclose the flaw before an attacker finds it independently.
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
Aztec, which controls the disclosure timetable and presents a critical soundness defect as the intended yield of its own alpha process, and competing rollups that can point to single-prover risk when courting the same institutional users.
Every material detail comes from Aztec's own advisory, including the claim that no other critical findings exist and that the flaw was found internally on 27 July 2026, a date roughly two months before publication that the company has not explained, and no outside auditor has independently confirmed the scope or that no exploitation occurred.
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
The exposure sits with anyone holding value inside a zero-knowledge rollup whose security reduces entirely to circuit correctness, because a soundness defect lets an attacker mint or move state that the verifier accepts as valid, and no honest node can object. Privacy rollups carry the sharpest version of this, since encrypted state makes anomalous balances harder for outside observers to spot early. The precedent is Aztec's own V4 cycle: disclosure timed to an upgrade, a user withdrawal window, and a patch one release later, with no loss reported. The likelier outcome over the coming months is that competing privacy and general-purpose rollups respond with proof-system diversity, multi-prover verification and explicit exit guarantees, and that institutional users demand these before committing size, which slows deposit growth into single-prover networks. The read depends on the V6 fix arriving without an incident in between. It would be proven wrong if an attacker exploits the V5 flaw before the patch, which would push the question from design practice to loss recovery.
What to watch
Observations to monitor, not financial advice.
Synthesized from: Aztec Network · Aztec Network · Aztec Network · The Defiant
Comments
0No comments yet.