CVE-2026-73541
High 8.3No known exploitationFix availableTempo fee sponsorship in mpp bounds each transaction but not aggregate exposure, allowing concurrent sponsor-wallet drain
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 49% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
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.
Weakness: CWE-770
Patching and mitigation
- Patch status
- Fix available (source: NVD (reference tagged Patch))
- Fix documented (source date)
- Mitigation
- Disable Tempo fee sponsorship by setting "fee_payer" => false (the default), so the client pays its own gas and the sponsor wallet is never committed. Where sponsorship must stay enabled, lowering max_total_fee and max_validity_window_seconds reduces the exposure each concurrent request can commit and how long it stays outstanding, without bounding the aggregate. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| ZenHive | mpp | from 0.2.0 before 0.12.0 | 0.12.0 | CVE Program |
| ZenHive | mpp | from d29d54e507918db00a5b65d90136b73166c017d7 before ddc46868fba57ccebb567c04709812b466123076 | ddc46868fba57ccebb567c04709812b466123076 | CVE Program |
| zenhive | machine_payments_protocol | from 0.2.0 before 0.12.0 | 0.12.0 | NIST NVD |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by NVD (reference tagged Patch)
Vendor guidance and references
- EEF CNA record for CVE-2026-73541 (opens in a new tab)mitigation, related, third party advisory
- Fix commit ddc4686 in ZenHive/mpp (opens in a new tab)patch
- https://github.com/ZenHive/mpp/security/advisories/GHSA-j4j7-7xpr-c7cr (opens in a new tab)related, vendor advisory, vendor-advisory
- OSV record EEF-CVE-2026-73541 (opens in a new tab)mitigation, related, third party advisory
- Introducing commit d29d54e in ZenHive/mpp (opens in a new tab)related