CVE-2026-48100

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-88359 (ENISA EUVD)Source: ENISA EUVD

8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.7Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

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 v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
70
EG Risk 70/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity87% × 45%
Impact severity (EG Severity): CVSS 8.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.7): severity, escalated by confirmed exploitation. This CVE's 8.7 is its impact severity (EG Severity), not escalated.

EG Severity
8.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 28, 2026

Last Modified

September 30, 2026

Advisory Details (1)

Auto-updated Sep 28, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

agg_agg trailing message slots are unconstrained and allow forged burn messages · Advisory · polybase/payy · GitHub

https://github.com/polybase/payy/security/advisories/GHSA-fhxc-63vg-9gwr

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 48× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  4. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  6. 2026-10-27 19:52 UTCEG score recompute
  7. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-25 14:23 UTCEG score recompute
  11. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-20 19:03 UTCEG score recompute
  16. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-18 03:35 UTCEG score recompute
  20. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-10-17 12:30 UTCEG score recompute
  22. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
Show 34 more
  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-10-12 16:01 UTCEG score recompute
  3. 2026-10-11 19:44 UTCEG score recompute
  4. 2026-10-11 16:58 UTCEG score recompute
  5. 2026-10-11 14:23 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-10-11 12:53 UTCEG score recompute
  8. 2026-10-11 00:39 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-10 00:18 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-08 22:55 UTCEG score recompute
  13. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-08 10:45 UTCEG score recompute
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-06 22:15 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-05 21:49 UTCEG score recompute
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-05 09:40 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-10-03 21:11 UTCEG score recompute
  23. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-10-02 20:50 UTCEG score recompute
  25. 2026-10-01 20:30 UTCEG score recompute
  26. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-09-30 19:00 UTCEG score recompute
  28. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  29. 2026-09-29 18:41 UTCEG score recompute
  30. 2026-09-29 06:29 UTCEG score recompute
  31. 2026-09-28 18:20 UTCEG score recompute
  32. 2026-09-28 17:34 UTCEG score recompute
  33. 2026-09-28 16:53 UTCEG score recomputeFirst assessed: 8.7 HIGH
  34. 2026-09-28 16:51 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48100?
CVE-2026-48100 is a high-severity vulnerability; its CVE record was published on September 28, 2026. 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…
When was the CVE record for CVE-2026-48100 published?
The CVE record for CVE-2026-48100 was published on September 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-48100 actively exploited?
CVE-2026-48100 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48100?
CVE-2026-48100 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48100?
The CVE record for CVE-2026-48100 names the fix: "This issue has been patched in version 1.3.0."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-48100

Explore →

Is Your Infrastructure Affected by CVE-2026-48100?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs