CVE-2026-48100 Details
Description
Payy is an Ethereum L2 zk-rollup for privacy preserving and regulatory compliant transactions. Prior to version 1.3.0, agg_agg forwards the compacted message stream from its inner proofs into a public messages: [Field; 1000] array, but it never checks that the unused tail of the outer array is zero. A registered prover can build a valid agg_final proof for an approved rollup block while inserting an extra burn message after the real messages. RollupV1.verifyRollup() then parses that public input as a normal burn and transfers USDC from the rollup contract to the attacker. This is a severe circuit soundness failure: the proof system accepts a public statement whose messages array is not fully derived from the verified inner proofs. On the current deployment, verifyRollup() is restricted to the existing allowlisted prover, so a fresh public caller cannot submit the invalid proof directly. That gate limits who can reach L1 today; it does not make the circuit statement sound. The issue becomes permissionless under the prover model described in the Payy whitepaper. Section 3.3.2 states: "To join as a prover, the prover is required to submit a small stake", and Section 3.3.1 states that if a prover fails to submit, "other nodes can submit the block proof instead." In that model, an attacker only needs to become a registered prover and use public validator approval data for an already approved block. This issue has been patched in version 1.3.0.
A critical circuit soundness vulnerability has been identified in Payy, an Ethereum Layer 2 zk-rollup solution, prior to version 1.3.0. The issue arises in the 'agg_agg' component, which improperly handles the public message array by failing to verify that unused slots are zero. This oversight allows a registered prover to inject a fraudulent burn message into the proof, which is then processed as a legitimate transaction, transferring USDC from the rollup contract to the attacker. The vulnerability exploits a flaw in the proof system's verification process, creating a scenario where unauthorized messages can be introduced and accepted as valid.
Users should update to Payy version 1.3.0 or later, where this vulnerability has been patched.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 28, 2026CISA-ADP
Assessed Sep 28, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/polybase/payy/security/advisories/GHSA-fhxc-63vg-9gwr | CISA-ADP | AdvisoryExploitRemedyVendor |
| https://github.com/polybase/payy/security/advisories/GHSA-fhxc-63vg-9gwr | [email protected] | AdvisoryExploitRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-349 | Acceptance of Extraneous Untrusted Data With Trusted Data | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Polybase Payy | zk-circuits-v1.1.12 |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 28, 2026 | CVE Modified | CISA-ADP |
| Sep 28, 2026 | New CVE Received | [email protected] |
Volerion