Back to CVE records
High 8.7Published Sep 28, 2026

CVE-2026-48100Payy: agg_agg trailing message slots are unconstrained and allow forged burn messages

Updated under an hour ago ()

Does this affect you?

It affects polybase payy. Add what you run to find out whether that includes you.

EPSS puts the chance of exploitation in the next 30 days at 0.18%, higher than 7% of scored CVEs.

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.

CVSS
8.7 HIGH (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Weakness (CWE)
CWE-349
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
0.18% (percentile 7)
Assigned by
GitHub_M
NVD analysis
Deferred
Record last updated
Sep 28, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
polybase payy
polybase:payy (from the name)
before 1.3.0
CNA record

References

  • x-refsource-confirm

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.