CVE-2026-73829: ZenHive mpp · Time-of-check Time-of-use (TOCTOU) Race Condition
Affects ZenHive mppSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 0.6.1 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.6.1, 46c5b0e1311da7d92190dc7d9ea89027a1d365e9
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade mpp to 0.6.1; mpp to 46c5b0e1311da7d92190dc7d9ea89027a1d365e9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ZenHivempp | Affected
| Fixed in
|
| ZenHivempp | Affected
| Fixed in
|
Hexmpppkg:hex/mppOther threats | Affected
| Fixed in
|
CPE configurations (1)
cpe:2.3:a:ZenHive:mpp:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
If you cannot patch yet, users should consider disabling or not configuring a dedup store for the hash credential path to avoid replay protection issues, or use the type="transaction" path which uses atomic operations. Monitor vendor communications for an official fix or update.
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.