CVE-2026-67581: ZenHive mpp · Authentication Bypass by Capture-replay
Affects ZenHive mppSource CVE Database V5
Not known to be exploited · CVSS 8.7 High : upgrade to 0.6.3 soon.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.6.3, ecc038088b1cda09ad8a84acc6cc112addb4a68f
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/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.3; mpp to ecc038088b1cda09ad8a84acc6cc112addb4a68f.
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 implementing additional verification mechanisms that bind proofs to specific challenges and track prior use to prevent replay attacks. Monitoring for unusual repeated use of the same transaction hashes may help detect exploitation attempts.
Description
Authentication Bypass by Capture-replay in ZenHive mpp allows an unauthenticated remote client to obtain paid resources by resubmitting one settled on-chain transfer. MPP.Methods.EVM.verify/2 accepts a transaction-hash credential and matches a transfer purely on token, to and amount (ERC-20) or to and value (native). It binds the proof neither to the challenge being verified nor to any record of prior use, and the generic MPP.Plug dedup store keys on challenge.id, which is regenerated for every 402 response. On a static-price route, a single historical transfer matching the charge therefore satisfies an unbounded number of later charges, including transfers an attacker can read off a public block explorer. This issue affects mpp: from 0.3.0 before 0.6.3.