Skip to content
Applications

CVE-2026-59694

8.3
High
EPSS 0.52%Patch availableJul 17, 2026

Unauthenticated clients can inflate gas fees via forged EIP-2930 access lists.

common questions

Is CVE-2026-59694 being exploited?

Not confirmed. CVE-2026-59694 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.52% probability of exploitation in the next 30 days.

How severe is CVE-2026-59694?

CVE-2026-59694 is rated High with a CVSS score of 8.3. 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-59694?

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

What does CVE-2026-59694 affect?

CVE-2026-59694 affects ZenHive mpp (Elixir) < 0.6.0, Services using mpp with fee_payer: true, Fee-payer wallets co-signing EIP-2930 transactions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-59694?

Upgrade to mpp >=0.6.0; validate/reject large access-lists; restrict co-signing.

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.6.0Services using mpp with fee_payer: trueFee-payer wallets co-signing EIP-2930 transactions
impact

Remote attacker can cause fee-payer to pay massively inflated gas per transaction, draining sponsor wallets and destroying margins.

action required

Immediate action required

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

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