CVE-2026-73136 json
Static memo configuration in mpp Tempo disables per-challenge attribution binding, enabling third-party replay
published 4mo ago modified 2mo ago also EEF-CVE-2026-73136 , EUVD-2026-62592 , GHSA-34g7-vx6g-82mq
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2026-73136 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.60% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.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 |
| CNA | 4.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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| hex | mpp | >=0.6.1, <0.6.4 |
0.6.4 |
Affected products
- ZenHive mpp
Classification
- Weakness
-
- CWE-294 Authentication Bypass by Capture-replay
References
-
github.com
/ZenHive/mpp/commit/2207d7f456ae14c1d3fcacc6f635bf4f8cee1a34
patch
-
github.com
/ZenHive/mpp/security/advisories/GHSA-34g7-vx6g-82mq
vendor-advisory, related, advisory
-
cna.erlef.org
/cves/CVE-2026-73136.html
related, third-party-advisory, web
-
osv.dev
/vulnerability/EEF-CVE-2026-73136
related, third-party-advisory
-
hex.pm
/packages/mpp
package
Sources
- CVE List CVE-2026-73136
- NVD CVE-2026-73136
- OSV EEF-CVE-2026-73136
- Maintainer advisory GHSA-34g7-vx6g-82mq
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of ZenHive/mpp published their own advisory on GitHub. Reviewed sources take precedence over it.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.