Morning Edition · Thursday, September 24, 2026Published at 1:46 AM EDT · New York
Core contributors found the defect through internal artificial-intelligence-assisted auditing, cannot rule out earlier exploitation, and have deferred the fix to the next network version.
.jpg)
Aztec, the privacy-focused layer-2 network on Ethereum, has disclosed a critical vulnerability in the proving system of its Alpha V5 release. By the project's own description, an attacker could construct a proof that passes verification for a transaction the network is supposed to reject, and that transaction could then produce a state change outside the rules V5 is meant to enforce. Contributors say they cannot determine whether anyone exploited the flaw before they found it, and they are telling users to treat funds, applications and contract state on V5 as exposed until incident response finishes and operators complete the required network actions. The repair is planned for V6.
The category matters more than the individual bug. A smart-contract exploit abuses code that runs correctly. A soundness defect breaks the check that decides what counts as valid in the first place. On most rollups, validators re-execute transactions and can catch an invalid state root. On a network built to keep transaction contents private, that fallback is weaker by design, because the data needed to re-execute a transaction is the same data the system is built to hide.
Aztec says the finding came from internal auditing assisted by artificial-intelligence tooling, which creates a risk in both directions. The same capability that lets reviewers sweep proving code at scale is available to anyone looking for the next unsound constraint, and the first published result of that sweep was a critical flaw in a live network holding user funds.
The disclosure arrives while competitors make the same case to institutions. Miden has announced its PriFi stack for private digital finance and a self-custodial private wallet called Bread, built on client-side execution. Privacy networks are now selling confidentiality as a prerequisite for serious on-chain business, which means the proof system is not a technical detail for their buyers. It is the entire security argument.
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
Competing privacy networks selling institutional confidentiality, including Miden, gain a documented failure at a rival's verifier, while Aztec gains reputational credit for disclosing a soundness defect before any loss was proven.
Every material detail comes from Aztec's own disclosure and no independent researcher has confirmed the flaw or any exploitation, and the post does not quantify how much value sits on the Alpha-stage V5 network, which is what separates a serious exposure from a contained testing result, per the project's notice.
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
Users and applications on Aztec's V5 network carry direct exposure, because a forged proof could move state without anyone detecting the move by re-executing hidden transactions. For the wider privacy sector the exposure runs through credibility: institutions evaluating confidential execution now have a documented case where the verifier, not the contract, was the weak point, and diligence will shift toward proof-system audits, fallback options and proof diversity rather than contract review alone.
What to watch
Observations to monitor, not financial advice.
Synthesized from: Aztec Network · Aztec Network · Miden · Miden
Comments
0No comments yet.