Is CVE-2026-73541 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-73541 being exploited in the wild.

How severe is CVE-2026-73541?

High severity, with a CVSS score of 8.2, published 19 August 2026.

Which products and versions are affected?

ZenHive Mpp 0.2.0 before 0.12.0.

Is there a fix for CVE-2026-73541?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-73541 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-73541?

Check whether you run ZenHive Machine Payments Protocol or ZenHive Mpp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-73541: ZenHive mpp resource exhaustion via concurrent sponsored payments

CVE-2026-73541 · Severity: high · CVSS 8.2 · Published 2026-08-19

ZenHive mpp is a blockchain payment library that allows sponsors to subsidize transaction fees for users. An unauthenticated attacker can exploit the lack of concurrent request limits to send many distinct sponsored transactions simultaneously, draining the sponsor's fee budget and blocking legitimate payments. Once the budget is empty, all sponsored transactions fail, denying service to authorized users.

Technologies: ZenHive Machine Payments Protocol, ZenHive Mpp. Vendors: ZenHive.

Quick answers

Is CVE-2026-73541 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-73541 being exploited in the wild.
How severe is CVE-2026-73541?: High severity, with a CVSS score of 8.2, published 19 August 2026.
Which products and versions are affected?: ZenHive Mpp 0.2.0 before 0.12.0.
Is there a fix for CVE-2026-73541?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-73541 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-73541?: Check whether you run ZenHive Machine Payments Protocol or ZenHive Mpp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a resource exhaustion flaw (CWE-770) in the fee-payer policy enforcement of ZenHive mpp. The FeePayerPolicy.Methods.Tempo component enforces per-transaction limits (max_gas, max_fee_per_gas, max_priority_fee_per_gas, max_total_fee budget) but does not track exposure across concurrent requests. The reserve_hash_atomic/2 function uses transaction hash as a key, preventing only duplicate broadcast of the same signed transaction, not N distinct transactions with different nonces. An unauthenticated remote client can send many concurrent sponsored transactions, each within individual limits but collectively exceeding the sponsor's budget within the default 900-second validity window. An attacker can drain the fee-payer wallet and deny service to legitimate users. Fixed in version 0.12.0.

Affected products

ZenHive mpp 0.2.0 before 0.12.0

Timeline

2026-08-19: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.