CVE-2026-73136
Last modified
CVE-2026-73136 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 0.54% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Zenhive | Machine Payments Protocol | >= 0.6.1, < 0.6.4 |
References
- https://cna.erlef.org/cves/CVE-2026-73136.htmlThird Party Advisory
- https://osv.dev/vulnerability/EEF-CVE-2026-73136Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-73136?
How severe is CVE-2026-73136?
How do I fix CVE-2026-73136?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-73111Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-73112Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2026-7312CWE‑522: Insufficiently Protected Credentials in web service…7.5
- CVE-2026-73122A flaw was found in the multicloud-operators-channel compone…7.7
- CVE-2026-73125Ebyte device web management interface does not consistently …9.8
- CVE-2026-7313CWE‑522: Insufficiently Protected Credentials in web service…4.9
- CVE-2026-73137A flaw was found in the multicloud-operators-subscription co…7.7
- CVE-2026-7314A vulnerability was detected in eiceblue spire-doc-mcp-serve…7.3
- CVE-2026-73140Affected versions of cti-transmute fail to apply comment-lev…5.3
- CVE-2026-7315A flaw has been found in eiceblue spire-pdf-mcp-server 0.1.1…7.3
- CVE-2026-73155Affected versions of cti-transmute allow authenticated users…5.3
- CVE-2026-73156Affected versions of cti-transmute fail to HTML-escape attac…5.3
Are you affected by CVE-2026-73136?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
