mpp: Authentication Bypass by Capture-replay
CVE-2026-73136 is a high-severity authentication bypass by capture-replay vulnerability in mpp from ZenHive, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 0.6.4, 2207d7f456ae14c1d3fcacc6f635bf4f8cee1a34 as the first without the flaw, so updating mpp to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.6% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update mpp to 0.6.4 or 2207d7f456ae14c1d3fcacc6f635bf4f8cee1a34, whichever matches your release line, or a later version.
- Update Machine Payments Protocol to 0.6.4 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| ZenHive | mpp | 0.6.1 up to, but not including, 0.6.4; 542a525563c2fcedd670b593437deca81c6797a4 up to, but not including, 2207d7f456ae14c1d3fcacc6f635bf4f8cee1a34 | 0.6.4, 2207d7f456ae14c1d3fcacc6f635bf4f8cee1a34 |
| Zenhive | Machine Payments Protocol | 0.6.1 up to, but not including, 0.6.4 | 0.6.4 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.2 | High | CNA |
| CVSS 3.1 | 7.5 | High | NVD |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Authentication Bypass by Capture-replay
A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).
How developers prevent this class of flaw
- Utilize some sequence or time stamping functionality along with a checksum which takes this into account in order to ensure that messages can be parsed only once.
- Since any attacker who can listen to traffic can see sequence numbers, it is necessary to sign messages with some kind of cryptography to ensure that sequence numbers are not simply doctored along with content.
More Authentication Bypass by Capture-replay vulnerabilities (CWE-294)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Third-party and government advisories
- cna.erlef.org/cves/CVE-2026-73136.htmlThird Party Advisory
- osv.dev/vulnerability/EEF-CVE-2026-73136Third Party Advisory
Other vulnerabilities in mpp
- 7.1 High severity
- 8.2 High severity
- 8.3 High severity
- 8.3 High severity
- 8.2 High severity
- 7.5 High severity
Recent Authentication Bypass by Capture-replay vulnerabilities
- 7.4 High severity
- 7.7 High severity
- 8.1 High severity
- 8.1 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.