CVE-2026-73829: Non-atomic hash-credential dedup in mpp Tempo allows replay of a confirmed payment under a concurrent race

Severity: low (CVSS 3.7 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-08-19 · updated 2026-09-10
Weakness: CWE-367

Description

Time-of-check Time-of-use (TOCTOU) Race Condition in ZenHive mpp allows an unauthenticated remote client to redeem one confirmed on-chain payment for multiple paid-resource accesses. The type="hash" credential path in MPP.Methods.Tempo.verify/2 guards against replay with a non-atomic check-then-mark sequence: check_hash_unused/2 reads the dedup store, an eth_getTransactionReceipt round trip verifies the payment on chain, and only then does mark_hash_used/2 write the mark. Concurrent requests carrying the same settled payment hash all pass the read before any of them writes, so each is issued a receipt. The store's atomic check_and_mark/2 primitive is available and used by the type="transaction" path, but the hash path calls plain get and put even when the configured store implements it. Exploitation requires a dedup store to be configured; the default nil store is stateless and documented as offering no replay protection at all. This issue affects mpp: from 0.2.0 before 0.6.1.

Affected products

ZenHive Machine Payments Protocol: from 0.2.0 before 0.6.1 — fixed in 0.6.1

How to fix

Upgrade to a fixed version: ZenHive Machine Payments Protocol 0.6.1. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-73829 or the next vulnerability affects your stack