Skip to content
Applications

CVE-2026-73136

8.2
High
EPSS 0.42%Patch availableAug 20, 2026

Auth bypass via replayed public transfer lets attacker claim others' paid resources.

common questions

Is CVE-2026-73136 being exploited?

Not confirmed. CVE-2026-73136 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-73136?

CVE-2026-73136 is rated High with a CVSS score of 8.2. 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-73136?

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

What does CVE-2026-73136 affect?

CVE-2026-73136 affects ZenHive mpp >=0.6.1 and <0.6.4, MPP.Methods.Tempo module. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-73136?

Upgrade to ZenHive mpp 0.6.4 and avoid static memo configs; validate sender binding.

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

executive summary
technical analysis
affected
ZenHive mpp >=0.6.1 and <0.6.4MPP.Methods.Tempo module
impact

Unauthenticated attacker can replay public settled Tempo transfers to obtain paid resources, bypassing sender authentication and attribution nonce checks.

action required

Patch when possible

affected versions
ZenHive mpp
  • affected>= 0.6.1 and < 0.6.4
  • affected>= 542a525563c2fcedd670b593437deca81c6797a4 and < 2207d7f456ae14c1d3fcacc6f635bf4f8cee1a34

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