Skip to content
Applications

CVE-2026-73541

8.3
High
EPSS 0.42%Patch availableAug 20, 2026

Unauthenticated actors can drain sponsored fee-payer wallets via concurrent payments.

common questions

Is CVE-2026-73541 being exploited?

Not confirmed. CVE-2026-73541 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.42% probability of exploitation in the next 30 days.

How severe is CVE-2026-73541?

CVE-2026-73541 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-73541?

Yes. A fix has been recorded for CVE-2026-73541. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-73541 affect?

CVE-2026-73541 affects ZenHive mpp 0.2.0 - 0.11.x, Applications using mpp sponsored payments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73541?

Upgrade to mpp >=0.12.0; enforce throttling and per-sponsor exposure caps.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
ZenHive mpp 0.2.0 - 0.11.xApplications using mpp sponsored payments
impact

Remote unauthenticated attacker can submit many sponsored transactions to exhaust a fee-payer wallet, causing financial loss and denial of service for legitimate payers.

action required

Immediate action required

affected versions
ZenHive mpp
  • affected>= 0.2.0 and < 0.12.0
  • affected>= d29d54e507918db00a5b65d90136b73166c017d7 and < ddc46868fba57ccebb567c04709812b466123076

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free