Skip to main content
VulnerabilityPublished

CVE-2026-73541: ZenHive mpp · Unthrottled Resource Allocation

Affects ZenHive mppSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 0.12.0 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.12.0, ddc46868fba57ccebb567c04709812b466123076
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade mpp to 0.12.0; mpp to ddc46868fba57ccebb567c04709812b466123076.

Affected software

ProductAffectedFixed in
ZenHivemppAffected
  • >=0.2.0 <0.12.0
Fixed in
  • 0.12.0
ZenHivemppAffected
  • ≥ d29d54e507918db00a5b65d90136b73166c017d7, < ddc46868fba57ccebb567c04709812b466123076
Fixed in
  • ddc46868fba57ccebb567c04709812b466123076
Hexmpppkg:hex/mppOther threatsAffected
  • >=0.2.0 <0.12.0
Fixed in
  • 0.12.0

CPE configurations (1)

  • cpe:2.3:a:ZenHive:mpp:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…