Skip to content

CVE-2026-73541 Tempo fee sponsorship in mpp bounds each transaction but not aggregate exposure, allowing concurrent sponsor-wallet drain

HighCVSS 8.3 EPSS 0.59%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: total

Description

Allocation of Resources Without Limits or Throttling in ZenHive mpp allows an unauthenticated remote client to drain the fee-payer wallet through concurrent sponsored payments, denying service to legitimate payers once it is empty.

MPP.Methods.Tempo.FeePayerPolicy enforces its ceilings (max_gas, max_fee_per_gas, max_priority_fee_per_gas, the worst-case gas_limit * max_fee_per_gas <= max_total_fee budget cap, and a validity window) against one transaction at a time, and nothing accounts for exposure across concurrent requests. reserve_hash_atomic/2 is keyed on the transaction hash, so it prevents duplicate broadcast of the same signed transaction but not N distinct sponsored transactions carrying distinct expiring nonces. Committed sponsor exposure is therefore N times max_total_fee, bounded by nothing in the library, and the default 900 second validity window lets co-signed transactions stay broadcastable and uncounted for that entire period.

This issue affects mpp: from 0.2.0 before 0.12.0.

Upgrade path

2 packages: 2 fixed.

PackageAffectedFixed inStatus
zenhive machine payments protocol >= 0.2.0, < 0.12.0 0.12.0 Fixed
zenhive mpp >= 0.2.0, < 0.12.0; >= d29d54e507918db00a5b65d90136b73166c017d7, < ddc46868fba57ccebb567c04709812b466123076 0.12.0, ddc46868fba57ccebb567c04709812b466123076 Fixed

Affected products

ProductAffected versionsFixed in
zenhive machine payments protocol >= 0.2.0, < 0.12.0 0.12.0
zenhive mpp >= 0.2.0, < 0.12.0 0.12.0
zenhive mpp >= d29d54e507918db00a5b65d90136b73166c017d7, < ddc46868fba57ccebb567c04709812b466123076 ddc46868fba57ccebb567c04709812b466123076

References