PoC Monitor
← All CVEs
CVE-2026-73136published 19 Aug 2026 17:19 UTCData: JSON · API

ZenHive mpp

Static memo configuration in mpp Tempo disables per-challenge attribution binding, enabling third-party replay

Authentication Bypass by Capture-replay in ZenHive mpp allows an unauthenticated third party to obtain paid resources by replaying a transfer settled by an unrelated payer. MPP.Methods.Tempo normally binds a settled TIP-20 TransferWithMemo to the specific challenge under verification through an attribution nonce carried in the memo. When a static "memo" is configured in method_config, check_matched_memo_binding/3 returns the match unconditionally and that binding is skipped, leaving only token, recipient, amount and the static memo value to match on. The static memo is echoed in every unauthenticated 402 response and Tempo transfers are public, so an attacker can take any matching transfer paid by a legitimate customer, request a fresh challenge for the same route, and present that transaction hash as a type="hash" credential. The hash path performs no sender or signature check tying the presenter to the wallet that broadcast the transfer. This issue affects mpp: from 0.6.1 before 0.6.4.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.2high · scored by CNA · CWE-294
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

ZenHive mpp
  • >= 0.6.1, < 0.6.4

Fixed in 0.6.4

ZenHive mpp
  • >= 542a525563c2fcedd670b593437deca81c6797a4, < 2207d7f456ae14c1d3fcacc6f635bf4f8cee1a34

Fixed in 2207d7f456ae14c1d3fcacc6f635bf4f8cee1a34

Mitigation

Upgrade mpp to 0.6.4 or later.

Upgrade mpp to 2207d7f456ae14c1d3fcacc6f635bf4f8cee1a34 or later.

Workaround

Remove the static "memo" from the Tempo method_config so verification falls back to the default per-challenge attribution binding, which ties each settled transfer to the challenge being verified. Where a static memo must be kept, configure a dedup store (for example MPP.Tempo.ConCacheStore) with a TTL at least as long as the challenge expiry, which reduces unlimited replay to a race on the transaction hash rather than closing it.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published19 Aug 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.