SEPTEMBER 15, 2026
Live Feed
Back to database
Case File

CVE-2026-73829

LOW · CVSS 3.7 EPSS 0.19% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-08-19 · Last synced 2026-09-15

CyberRota Analysis

AI-Generated

The ZenHive mpp is vulnerable due to a Time-of-check Time-of-use (TOCTOU) race condition that allows unauthenticated remote clients to exploit confirmed on-chain payments for multiple accesses to paid resources. This vulnerability arises from a non-atomic sequence in the credential verification process, enabling concurrent requests to bypass proper deduplication checks. Organizations using affected versions (0.2.0 to before 0.6.1) with a configured deduplication store should prioritize patching to prevent potential financial losses from unauthorized resource access.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Detected Signals
exploit

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-73829
Severity
LOW
CVSS
3.7
EPSS
0.19%

Original NVD 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.

Related CVEs

Other vulnerabilities affecting the same vendor(s)