CVE-2026-73136CWE-294

CVE-2026-73136

High · published August 19, 2026

CVSS v3.1
7.5
EPSS
1%
Percentile
47.8
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
7.5 · HIGH
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
CVSS v4.0
8.2 · 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
EPSS
0.00595 · 47.8th percentile
Weakness
CWE-294 · Authentication Bypass by Capture-replay
Published
2026-08-19T22:17Z
Affected products (1)
ProductVersionsFixed in
zenhive/machine_payments_protocol≥ 0.6.1, < 0.6.40.6.4
References (4)
EPSS history
Timeline
  • 19 AUG 17:19Z
    Static memo configuration in mpp Tempo disables per-challenge attribution binding, enabling third-party replay
    cvelistv5