Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed MPP Tempo sponsorship endpoint
-
DeliveryCraft 0x76 envelope with seven aa_authorization_list entries
-
ExploitSubmit request unauthenticated to sponsorship server
-
ExecutionFeePayerPolicy skips aa_authorization_list validation
-
PersistServer co-signs and broadcasts; intrinsic gas billed to sponsor at ~40x
-
ImpactPersistent EIP-7702 set-code delegations written on-chain to attacker accounts
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V2 - Validation and Business Logic Input size validation
|
| Exploitation Conditions | The target must be running ZenHive mpp 0.2.0-0.16.0 with the MPP.Methods.Tempo payment sponsorship feature active and exposed to network clients. No authentication is required on the sponsorship endpoint itself - the vulnerable code path executes for any client-submitted 0x76 envelope. The CVSS 4.0 AT:P prerequisite is satisfied whenever a Tempo sponsorship service is deployed; servers not offering this feature are unaffected. The per-request gas cost multiplication is bounded by the server's configured gas_limit ceiling (limiting total financial loss per request), but within that ceiling an attacker can achieve the full ~40x amplification with seven delegation entries. There is no rate-limiting or client identification in the vulnerable code, so an attacker can submit requests repeatedly. The persistent EIP-7702 delegation side-effect requires no additional privilege beyond submitting a valid (but malicious) sponsorship request. |
| Impact | The CVSS 4.0 base score of 8.3 with vector AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L correctly characterises the threat. The AT:P (attack prerequisites) metric acknowledges that an MPP Tempo sponsorship service must be actively running - the sole prerequisite - after which any unauthenticated remote client can exploit the bypass with no complexity. The dual impact distinguishes this from a simple DoS: gas cost inflation drains the sponsor's on-chain budget at each request, while persistent EIP-7702 set-code delegations are effectively irreversible on-chain without further transactions and at further cost. Even a mid-sized municipal IT team in malbork operating a blockchain payment gateway built on mpp should treat this as urgent given the direct financial exposure and the difficulty of unwinding persistent account delegations. No EPSS data or CISA KEV listing is present in the provided intelligence; no public exploit code has been identified. The narrow deployment population (Elixir services actively sponsoring EIP-7702 Tempo payments) limits broad automated scanning, but any such deployment faces direct and quantifiable financial harm with each malicious request, constrained only by the configured gas_limit ceiling. |
| Exploit ScenarioDerived | An unauthenticated attacker with network access to an MPP Tempo sponsorship service constructs a 0x76 transaction envelope populated with seven EIP-7702 authorization entries signed by throwaway private keys, then submits it to the sponsorship endpoint. The server validates gas limits, fee budget, and access list but accepts the aa_authorization_list unchecked, co-signs the envelope, and pays roughly 1.88M gas instead of 46,575 - a ~40x inflation - while the EIP-7702 delegations are written on-chain as persistent set-code operations on the attacker's addresses at the sponsor's expense. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 06, 2026
Missing validation of the EIP-7702 aa_authorization_list field in ZenHive mpp's Tempo payment sponsorship module allows any unauthenticated remote client to inflate the fee-payer's gas cost by roughly 40x and to have the sponsor pay for persistent EIP-7702 set-code delegations on attacker-controlled Ethereum accounts. Versions 0.2.0 through 0.16.0 are affected; the FeePayerPolicy.measure/3 function validates gas fields, fee budget, validity window, and access list but never inspects the aa_authorization_list, so a client embedding seven throwaway delegation entries drives sponsored gas from approximately 46,575 to over 1,884,087. No public exploit has been identified at time of analysis, and a vendor patch is available in mpp 0.16.1.
RemediationAI
Upgrade mpp to version 0.16.1 or later, the vendor-released patch confirmed by the GitHub security advisory GHSA-5qrp-r24c-w6jr and patch commit 0482572b47e1ffe1537ab80ab613d47b92833c2d. The patch enforces that any sponsored 0x76 envelope must carry an empty aa_authorization_list and a matching or absent key-authorization field before the server co-signs. If an immediate upgrade is not possible, operators should restrict the Tempo payment sponsorship endpoint to a known-good, authenticated set of clients via network-layer ACLs or application-level authentication middleware, accepting the operational trade-off of reduced service availability until the patch is applied. Disabling the Tempo sponsorship feature entirely eliminates the attack surface with no code change required, at the cost of all sponsored-payment functionality.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
ZenHive mpp is an Elixir library implementing EIP-7702 Tempo payment sponsorship - a mechanism by which a fee-payer server co-signs and subsidizes gas costs for client-initiated Ethereum transactions. EIP-7702 introduced transaction type 0x76, which carries an aa_authorization_list allowing externally owned accounts (EOAs) to permanently delegate execution to smart contract bytecode via signed set-code operations. Each entry in that list incurs intrinsic gas cost, charged before the sponsored call executes. CWE-1284 (Improper Validation of Specified Quantity in Input) is the root cause: lib/mpp/methods/tempo/fee_payer_policy.ex checked all other client-controlled envelope fields - gas limits, maximum fee, validity window, access list, calldata - but omitted any bounds or emptiness check on aa_authorization_list. The fix in commit 0482572b adds check_authorization_list/1, which rejects any sponsored 0x76 envelope with a non-empty authorization list, and check_key_authorization/2, which enforces exact matching for the optional key-authorization field.
Know when Mpp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
Scope changes because the sponsor (fee-payer) is the harmed party, not the submitting client; no authentication required; persistent EIP-7702 delegations yield high integrity impact; gas depletion yields low availability impact.
Primary rating from Vendor (EEF).
CVSS VectorVendor: EEF
DescriptionCVE.org
Improper Validation of Specified Quantity in Input in ZenHive mpp allows an unauthenticated remote client to inflate the fee-payer's gas cost per sponsored payment by a large multiplier and to have the sponsor pay for EIP-7702 account delegations of the client's choosing.
When the server sponsors Tempo payments, MPP.Methods.Tempo.FeePayerPolicy.measure/3 in lib/mpp/methods/tempo/fee_payer_policy.ex bounds the gas fields, the fee budget, the validity window and the access list of the client-signed 0x76 envelope, but never reads its aa_authorization_list field. Every signed delegation in that list is charged as intrinsic gas before the payment call runs, so a client attaching delegations from throwaway authority keys makes the sponsor pay for them within the default gas_limit ceiling. At the reporter's default of seven entries the sponsored cost rises from about 46,575 gas to about 1,884,087 gas. Because each entry is applied as a persistent set-code delegation, a client can also upgrade its own accounts to delegated code at the sponsor's expense.
This issue affects mpp: from 0.2.0 before 0.16.1.
Technical POC Analysis
CVE-2026-82750 is an instance of CWE-1284, Improper Validation of Specified Quantity in Input.
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
1 PoC candidate from github (unverified)
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
ZenHive mpp's Tempo payment sponsorship module (versions 0.2.0-0.16.0) allows unauthenticated remote attackers to multiply transaction costs borne by fee sponsors up to 40-fold and force sponsor funding to be allocated to attacker-controlled account delegations. Organizations using affected versions face immediate financial risk through uncontrolled cost escalation in their blockchain payment infrastructure. No public exploit has been identified at time of analysis.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Gas-cost inflation and unauthorized access key provisioning in ZenHive mpp (versions 0.2.0 through 0.15.x) allows any un
Replay of settled EVM blockchain transaction hashes against ZenHive mpp versions 0.3.0-0.6.2 allows unauthenticated remo
Concurrent sponsored-payment flooding in ZenHive mpp (versions 0.2.0 through 0.12.0) allows an unauthenticated remote cl
Economic resource exhaustion in the ZenHive mpp Elixir library (versions 0.2.0 through 0.5.x) lets an unauthenticated re
Fee-payer wallet draining in ZenHive mpp (Elixir) 0.2.0-0.5.x lets an unauthenticated remote client empty the sponsor's
Capture-replay authentication bypass in ZenHive mpp versions 0.6.1-0.6.3 allows unauthenticated network attackers to cla
Wallet-draining denial of service in ZenHive mpp (Elixir library) versions 0.2.0 through 0.5.x affects deployments confi
Replay of a captured Tempo subscription credential in ZenHive mpp 0.14.0 through 0.16.1 lets an attacker who already hol
ZenHive mpp versions 0.14.0 through 0.16.1 fail to charge clients that hold an open payment channel, allowing an authent
Duplicate-submission gate bypass in the Tempo payment method of ZenHive mpp (versions 0.2.0 through 0.16.1) lets an unau
ZenHive mpp (MPP.Plug payment middleware for Elixir/Phoenix) versions 0.1.0 through 0.16.1 can allow a shared HTTP cache
Payment-replay protection in ZenHive mpp's Tempo hash-credential path is defeated by a TOCTOU race condition, allowing a
EUVD-2026-72148
GHSA-q4f3-jf9f-788f
NVD
CVE.org
EPSS
VulDB
Exploit-DB