CVE-2026-59695

HIGHPre-NVD 8.38.3
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:eef
Trending — 4 sources updated this weekElevated
8.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Improper Validation of Specified Quantity in Input in ZenHive mpp allows an unauthenticated remote client to drain the fee-payer wallet in a single request by naming an arbitrarily high gas price.

When the mpp Elixir library is configured as fee payer (fee_payer: true), MPP.Tempo.Transaction.cosign_fee_payer/3 re-signs the client-supplied base fields of the 0x76 AASigned envelope verbatim, including max_fee_per_gas and max_priority_fee_per_gas, without validating that they are within reasonable bounds. A malicious client embeds arbitrarily large values for these fields in the signed envelope. The server co-signs and broadcasts the transaction. The effective_gas_price billed against the fee-payer wallet is derived from the attacker-supplied ceilings, so the server pays those inflated per-gas rates out of its own wallet. A single crafted request can drain the wallet entirely, after which the server can no longer sponsor gas for legitimate payment requests.

This issue affects mpp: from 0.2.0 before 0.6.0.

CVSS v3
8.3
EG Score
8.3(low)
EPSS
22.3%
KEV
Not listed

Published

July 17, 2026

Last Modified

July 18, 2026

Advisory Details (4)

Auto-updated Jul 17, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic

OSV - Open Source Vulnerabilities

https://osv.dev/vulnerability/EEF-CVE-2026-59695
github Patch Available🟡 PoC Available

Gas Draining with no limit · Advisory · ZenHive/mpp · GitHub

https://github.com/ZenHive/mpp/security/advisories/GHSA-vv77-66rf-pm86
github_commit

commit 5d6338e23340 (ZenHive/mpp)

Fix landed in ZenHive/mpp commit 5d6338e23340 — awaiting tagged release

https://github.com/ZenHive/mpp/commit/5d6338e2334084c5f2a78cfcca474830733ed7e8
generic

Unbounded max_fee_per_gas in mpp Tempo fee-payer enables single-request wallet drain | Erlang Ecosystem Foundation CNA

https://cna.erlef.org/cves/CVE-2026-59695.html

Vendor Advisories for CVE-2026-59695(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
mpp0.2.0, 0.3.0, 0.3.1, 0.3.2, 0.4.00.6.0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 05:40 UTCEG score recompute
  9. 2026-07-18 05:40 UTCGHSA enrichment
  10. 2026-07-18 02:05 UTCGHSA enrichment
  11. 2026-07-18 01:54 UTCGHSA enrichment
  12. 2026-07-17 22:21 UTCGHSA enrichment
  13. 2026-07-17 14:01 UTCEG score recompute
  14. 2026-07-17 14:01 UTCGHSA enrichment
  15. 2026-07-17 13:02 UTCEG score recompute
  16. 2026-07-17 13:02 UTCGHSA enrichment
  17. 2026-07-17 12:00 UTCEG score recompute
  18. 2026-07-17 10:19 UTCEG score recompute
  19. 2026-07-17 10:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59695?
CVE-2026-59695 is a high vulnerability published on July 17, 2026. Improper Validation of Specified Quantity in Input in ZenHive mpp allows an unauthenticated remote client to drain the fee-payer wallet in a single request by naming an arbitrarily high gas price. When the mpp Elixir library is configured as fee payer (feepayer: true),…
When was CVE-2026-59695 disclosed?
CVE-2026-59695 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on July 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59695 actively exploited?
CVE-2026-59695 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 22.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59695?
CVE-2026-59695 has a CVSS v4.0 base score of 8.3 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-59695?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59695, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-59695

Explore →

Is Your Infrastructure Affected by CVE-2026-59695?

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