Skip to main content
VulnerabilityPublished Updated

CVE-2026-67581: ZenHive mpp · Authentication Bypass by Capture-replay

Affects mppSource GCVE Database

0
Authoritative record:CVE-2026-67581· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 0.6.3 soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.6.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade zenhive/mpp to 0.6.3.

Affected software

ProductAffectedFixed in
GitHubzenhive/mpppkg:github/zenhive/mppOther threatsAffected
  • <0.6.3 >=0.3.0
Fixed in
  • 0.6.3

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, avoid relying on transaction hash credentials alone for authentication and consider implementing additional mechanisms to bind proofs to specific challenges and prevent replay attacks.

Description

CVE-2026-67581 is an authentication bypass vulnerability in ZenHive mpp versions from 0.3.0 before 0.6.3. It allows an unauthenticated remote attacker to reuse a previously settled on-chain transfer to obtain paid resources without authorization. The vulnerability arises because the verification method accepts a transaction hash credential and matches transfers based only on token, recipient, and amount, without binding the proof to the specific challenge or preventing reuse. This enables replay attacks using publicly visible blockchain transactions.

References

Community reviews

Loading reviews…