Skip to content
Applications

CVE-2026-59252

8.2
High
EPSS 0.63%Patch availableJul 17, 2026

Unauthenticated clients can drain fee-payer wallet via crafted low-gas transactions.

common questions

Is CVE-2026-59252 being exploited?

Not confirmed. CVE-2026-59252 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.63% probability of exploitation in the next 30 days.

How severe is CVE-2026-59252?

CVE-2026-59252 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-59252?

Yes. A fix has been recorded for CVE-2026-59252. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-59252 affect?

CVE-2026-59252 affects ZenHive mpp (Elixir) >=0.2.0 and <0.6.0, Components using fee_payer: true and MPP.Methods.Tempo. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-59252?

Upgrade mpp to >=0.6.0; validate gas_limit server-side or disable fee_payer.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
ZenHive mpp (Elixir) >=0.2.0 and <0.6.0Components using fee_payer: true and MPP.Methods.Tempo
impact

Remote attackers can cause the fee-payer to pay burned gas, draining wallet and causing denial of service for sponsored payments.

action required

Immediate action required

affected versions
ZenHive mpp
  • affected>= 0.2.0 and < 0.6.0
  • affected>= d29d54e507918db00a5b65d90136b73166c017d7 and < d84e3e528db39654540c2035ea0fbdf7b950d3d1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free