How Scroll Fixed Its zkEVM Proof Verification Vulnerability

2026-11-12
How Scroll Fixed Its zkEVM Proof Verification Vulnerability

Scroll has addressed a zero-knowledge proof verification vulnerability through an emergency mainnet upgrade on November 10, 2026. 

The issue affected its Bundle proof verifier for Batch Version 10 and could potentially have allowed attackers to reuse previously valid proofs with altered public inputs. 

Although the flaw raised concerns about Layer 2 transaction integrity and withdrawal security, Scroll confirmed that it had not been exploited on mainnet. The incident highlights why proof verification remains essential to zkEVM security.

Key Takeaways

  • Emergency patch deployed: Scroll registered a corrected Bundle proof verifier for Batch Version 10 on November 10, 2026.

  • No reported exploitation: The vulnerability was disclosed through the bug-bounty programme on November 3, and Scroll says no malicious activity occurred.

  • Important security lesson: Zero-knowledge proofs must be securely linked to the exact public inputs they are designed to verify.

What Was the Scroll zkEVM Proof Verification Vulnerability?

How Scroll Fixed Its zkEVM Proof Verification Vulnerability

source by AI

Scroll is an Ethereum Layer 2 network that uses zero-knowledge rollup technology to process transactions and verify their validity more efficiently than executing every operation directly on Ethereum. 

Its security relies on cryptographic proofs that demonstrate whether batches of Layer 2 transactions have been processed correctly. 

These proofs are checked by smart contracts deployed on Ethereum before Scroll can finalise the corresponding state updates.

The reported vulnerability affected this verification process, specifically the on-chain Bundle proof verifier associated with Batch Version 10.

img_v3_02172_7a01bc13-f32f-4752-adfa-4ebb67683chu.jpg

How Did the Proof Replay Flaw Work?

According to the incident reports, older versions of the verifier interpreted the first four bytes of a caller-supplied proof as an EVM function selector when calling the OpenVM 2.0 Halo2 verifier.

An EVM function selector identifies which function a smart contract should execute. However, in this situation, the handling of those bytes created an unintended verification path.

If a proof started with a particular selector, it could bypass the intended fallback mechanism. This potentially allowed an attacker to take an older, previously valid proof and submit it alongside different public inputs.

The key problem was that the verifier did not adequately bind the proof to the specific batch information it was supposed to certify.

In practical terms, a proof that was valid for one set of data could potentially be reused to support a different state transition.

This is known as a proof replay vulnerability. Rather than breaking the underlying cryptographic mathematics, the flaw exploited how the verification contract interpreted and processed proof data.

Why Was This a Serious Security Concern?

For a zk-rollup, proof verification is one of the most important security boundaries between Layer 2 and Ethereum.

A successful verification allows a batch to be finalised and its corresponding state and withdrawal roots to be recognised. If an attacker could manipulate this process, they might potentially finalise arbitrary state roots or withdrawal roots.

That could undermine the integrity of the network and create opportunities for fraudulent withdrawals.

However, the reported exploit conditions were limited. An attacker would have needed licensed prover permissions, or the network would have had to enter forced-batch mode following seven consecutive days without finalisation.

These requirements reduced the available attack paths, but they did not make the underlying vulnerability harmless. A weakness in a rollup's proof verification mechanism still represents a significant protocol-level risk.

How Scroll Fixed the Vulnerability on November 10, 2026

How Scroll Fixed Its zkEVM Proof Verification Vulnerability

source by AI

Scroll responded by deploying a corrected verifier rather than relying solely on monitoring or restricting suspicious transactions.

The incident timeline shows how the project moved from vulnerability disclosure to an emergency mainnet remediation.

From Bug Report to Emergency Upgrade

November 3, 2026 – Vulnerability reported

The issue was reported through Scroll's bug-bounty programme. The report identified a weakness in the Bundle proof verifier deployed on Ethereum mainnet.

Investigation and containment

Scroll investigated the vulnerability and examined whether it had been exploited. According to the project, there was no evidence of malicious exploitation during the affected period.

November 10, 2026 – Patched verifier registered

Scroll deployed and registered a corrected Bundle proof verifier for Batch Version 10. The update addressed the problematic proof and selector handling, preventing previously valid proofs from being reused with altered public inputs.

Review of previous finalisations

Scroll also reviewed 748 finalisations that occurred while the affected contracts were active. Its investigation found that these finalisations used standard proofs.

This review was important because it helped determine whether the vulnerability had affected actual network operations rather than simply existing as a theoretical attack vector.

What Changed After the Patch?

The main objective of the upgrade was to restore the intended relationship between a cryptographic proof and the public inputs it verifies.

By correcting the verifier's handling of the proof data, Scroll closed the replay path that could have allowed an old proof to be accepted in a different context.

This demonstrates an important distinction in blockchain security: a proof can be mathematically valid but still be unsafe to reuse if the verification contract does not correctly check the data associated with it.

For Scroll, the emergency upgrade was therefore a protocol-level correction designed to protect the integrity of future batch finalisations.

Why the Vulnerability Did Not Lead to Reported Fund Losses

Despite the seriousness of the potential exploit, Scroll reported that the vulnerability was not exploited on mainnet.

Several factors helped limit the incident's impact.

Forced-Batch Mode Was Never Triggered

One of the reported exploit conditions involved the network entering forced-batch mode after seven consecutive days without finalisation.

Scroll stated that this condition never occurred during the exposure period.

Consequently, this particular route for exploiting the vulnerability was not available during the affected period.

Earlier Verifier Versions Were Not Affected

The vulnerability was associated with the relevant Batch Version 10 verifier deployment. According to the incident reporting, earlier versions of the verification contracts were unaffected.

This narrowed the scope of the issue and reduced the number of affected verification components.

No Malicious Finalisations Were Reported

Scroll's review of the 748 finalisations found that they used standard proofs. The project also stated that no exploitation had occurred.

Based on the available incident information, this was a contained protocol-security defect rather than a confirmed theft of cryptocurrency or fraudulent state-finalisation event.

However, the absence of reported exploitation should not be interpreted as proof that every component of a blockchain ecosystem is risk-free. Users and developers should continue monitoring security disclosures and protocol updates.

What the Scroll Incident Means for Ethereum Layer 2 Security

The incident highlights an important challenge for zero-knowledge rollups: cryptographic security depends on more than the mathematical strength of the proof system.

Even when a proof is correctly generated, vulnerabilities in the smart contract responsible for verifying it can introduce weaknesses.

Why Input Binding and Replay Protection Matter

Input binding ensures that a cryptographic proof is associated with the exact public data it is intended to validate. Without proper binding, a valid proof could potentially be reused in an unintended context.

Replay protection is equally important because it prevents previously authorised or verified data from being accepted again when the circumstances have changed.

For zkEVM developers, these considerations should be included in security audits alongside circuit soundness, smart contract permissions and transaction validation.

What Should Scroll Users and Developers Watch Next?

Following the November 10 upgrade, several areas deserve attention:

  • Verifier updates: Developers should confirm that their integrations use the corrected Batch Version 10 verification contracts.

  • Independent security reviews: Audits should examine proof handling, function selectors and public-input validation.

  • Protocol monitoring: Users should follow official Scroll announcements for additional security disclosures and upgrade requirements.

  • Withdrawal integrity: Developers and users should continue monitoring the security of withdrawal processes and state-root finalisation.

  • Bug-bounty programmes: Responsible vulnerability disclosure can help identify protocol weaknesses before malicious actors exploit them.

The broader lesson extends beyond Scroll. As Ethereum Layer 2 adoption grows, proof verification contracts will remain critical infrastructure. Strong cryptography must be supported by careful smart contract engineering, secure implementation and continuous testing.

BItrue Migration Reward.jpeg

Conclusion

Scroll's November 10, 2026, emergency upgrade addressed a significant zkEVM proof verification vulnerability affecting its Batch Version 10 Bundle verifier. 

Although the flaw could potentially have enabled proof replay and unauthorised state finalisation, Scroll reported no mainnet exploitation and found that 748 reviewed finalisations used standard proofs. 

The incident reinforces the importance of input binding, replay protection and independent security audits across Ethereum Layer 2 networks. For users exploring crypto markets, Bitrue offers a platform for easier and safer crypto trading. Always research projects, monitor security updates and manage your investment risks responsibly.

FAQ

What was the Scroll zkEVM vulnerability?

It was a proof verification flaw affecting Scroll's Bundle verifier for Batch Version 10. The issue could potentially have allowed an attacker to reuse an old valid zero-knowledge proof with different public inputs.

When did Scroll fix the proof verification vulnerability?

Scroll deployed and registered a patched Bundle proof verifier on Ethereum mainnet on November 10, 2026. The vulnerability had reportedly been submitted through its bug-bounty programme on November 3.

Was the Scroll vulnerability exploited?

No. Scroll stated that the vulnerability was not exploited on mainnet. Its investigation also reviewed 748 finalisations during the affected period and found that they used standard proofs.

Could the vulnerability have affected user funds?

Potentially, yes. If successfully exploited, the flaw could have allowed arbitrary state roots and withdrawal roots to be finalised, creating a risk of fraudulent withdrawals. However, Scroll reported no exploitation or resulting fund losses.

What does the Scroll security upgrade mean for Ethereum Layer 2 networks?

It highlights the importance of secure proof verification, correct public-input binding and replay protection. Other Layer 2 projects can use the incident as a reminder to strengthen smart contract audits and test their verification systems against unexpected proof inputs.

Disclaimer: The views expressed belong exclusively to the author and do not reflect the views of this platform. This platform and its affiliates disclaim any responsibility for the accuracy or suitability of the information provided. It is for informational purposes only and not intended as financial or investment advice.

Disclaimer: The content of this article does not constitute financial or investment advice.

Register now to claim a 6752 USDT newcomer's gift package

Join Bitrue for exclusive rewards

Register Now
register

Recommended

How to Earn 88% Swap Fees on PancakeSwap v3 and Infinity Pools
How to Earn 88% Swap Fees on PancakeSwap v3 and Infinity Pools

PancakeSwap's The Flip upgrade increases LP fee rewards to 88% on v3 and Infinity pools while cutting CAKE emissions by approximately 69%.

2026-11-17Read