Morning Edition · Thursday, August 27, 2026Published at 1:48 AM EDT · New York
Core contributors say an attacker could construct a proof that passes verification for a transaction the network should reject, and they cannot rule out that it was used before discovery.

Aztec, the privacy-focused layer-2 network on Ethereum, disclosed a critical vulnerability in the proving system behind its Alpha v5 release. According to the project's own disclosure, an attacker may be able to construct a proof that passes verification for a transaction the network is supposed to reject, which would let the chain accept a state transition outside its own rules. Core contributors found the flaw through internal review, and they say they cannot determine whether anyone exploited it beforehand. 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 different category of failure than a smart-contract bug. On a zero-knowledge rollup, the cryptographic proof itself certifies a transaction as valid, and there is no separate check behind it. If the verifier accepts an invalid proof, no amount of contract auditing would catch the error. The safeguard optimistic rollups rely on, independent re-execution of transactions by validators, does not exist in the same form here. That is why a soundness defect forces a network pause and a system upgrade rather than a patch to a single application.
This is not Aztec's first such disclosure. The project published a critical vulnerability notice for Alpha v4 earlier in its testing cycle and raised its bug bounty to $2 million. Both facts point to the same conclusion: this is alpha software, and the team treats pre-mainnet disclosure as the intended result of its review process, not as a failure.
This disclosure comes amid a broader wave of privacy-focused development. Aztec's own applications, including a live on-chain game and private decentralized finance (DeFi) integrations, run on the same proving stack that contains the flaw.
Aztec, which converts a severe defect into evidence that its staged alpha process and $2 million bounty work, and competing rollups that market verifier diversity.
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
Every detail here originates with Aztec's own disclosure and cannot be checked independently, and the contributors found the flaw on 27 July through internal AI-assisted auditing, meaning roughly a month passed between discovery and public 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
Proof soundness has become the single point of failure for privacy rollups, and standard audit methods cannot detect it. A zero-knowledge layer-2 network cannot catch an invalid state transition by re-running transactions the way other systems can, so users, application developers and bridge operators depend entirely on the prover team's internal review and on whatever emergency mechanism the network provides. The parties exposed are depositors and applications on Aztec v5 during the response window, and, more broadly, every rollup that markets proof verification as a stronger guarantee than validator honesty. The mitigating factor is that this was caught during the alpha phase, before user funds reached mainnet scale.
What to watch
Observations to monitor, not financial advice.
Synthesized from: Aztec Network · Aztec Network
Comments
0No comments yet.