Morning Edition · Friday, September 25, 2026Published at 1:49 AM EDT · New York
Core contributors found the defect through internal artificial-intelligence-assisted auditing on 27 July 2026, cannot rule out prior exploitation, and have deferred the fix to the next network version.

Aztec, the privacy-focused layer-2 network on Ethereum, has disclosed a critical vulnerability in the proving system 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, which would produce a state transition outside the rules the protocol intends to enforce. Contributors identified the defect on 27 July 2026 through internal auditing assisted by artificial intelligence, and they state they cannot determine whether anyone exploited it beforehand.
Aztec tells users to treat funds, applications and contract state on V5 as exposed to a protocol-level failure until incident response finishes and node operators complete the required network actions. The fix is planned for V6. Reviewers say internal and external human audits have completed without finding other critical or high-severity issues in V5, and that machine-assisted review continues.
This is the second consecutive Alpha version to carry a critical proving-system defect. Aztec disclosed a comparable flaw in Alpha V4 in March, with the patch shipped in the V5 release. The pattern matters because a soundness bug in a zero-knowledge proving system (cryptographic code that lets a network confirm a transaction is valid without re-executing it) is a different risk class from a smart-contract bug. Validators cannot catch it by re-executing transactions, since the fraudulent proof verifies correctly by construction. The network's Alpha V5 program has meanwhile been onboarding private applications, including a version of the on-chain game Dark Forest, so the exposed state is no longer purely experimental.
There is a second point worth noting. The defect was found by an internal audit process using artificial intelligence, the defensive counterpart to an argument now common in crypto security, where the same capability said to threaten cryptographic assumptions is also accelerating the discovery of implementation errors before attackers can exploit them.
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 gains reputationally by disclosing before an exploit rather than after one, and competing zero-knowledge rollups gain if buyers of confidential infrastructure conclude that soundness risk is concentrated in one team rather than in the whole proving-system category.
Everything here comes from Aztec's own disclosure with no external party able to confirm the severity, the discovery date, or the statement that prior exploitation cannot be ruled out, and the framing that Alpha software is supposed to surface such defects sits alongside the fact that this is the second consecutive version with a critical proving bug and that the fix is deferred to V6 rather than shipped.
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
Rollups and privacy networks that rely on validity proofs have no fallback when the prover itself is unsound, because re-execution by honest validators cannot detect a proof that verifies. Users of Aztec's Alpha V5 carry direct exposure to any state transition an attacker could have forged, and the broader cost lands on every zero-knowledge network competing for institutional confidentiality work, because buyers now have a second concrete instance of the risk to price. The competing outcome is that repeated self-disclosure before exploitation builds credibility, which would favor teams with mature audit programs over faster shippers.
What to watch
Observations to monitor, not financial advice.
Synthesized from: Aztec Network · Aztec Network · Aztec Network
Comments
0No comments yet.