Skip to content
Applications

CVE-2026-67581

8.7
High
EPSS 0.41%Patch availableAug 20, 2026

Auth bypass allows replay of on-chain transfer to access paid resources.

common questions

Is CVE-2026-67581 being exploited?

Not confirmed. CVE-2026-67581 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.

How severe is CVE-2026-67581?

CVE-2026-67581 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-67581?

Yes. A fix has been recorded for CVE-2026-67581. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-67581 affect?

CVE-2026-67581 affects ZenHive mpp 0.3.0 - 0.6.2, EVM.Methods.EVM.verify, MPP.Plug dedup store. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-67581?

Upgrade ZenHive mpp to >=0.6.3 and bind/verifiy proofs to challenge to prevent replay.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
ZenHive mpp 0.3.0 - 0.6.2EVM.Methods.EVM.verifyMPP.Plug dedup store
impact

Unauthenticated attacker can replay a public historical on-chain transfer to bypass payment checks and consume paid resources repeatedly.

action required

Immediate action required

affected versions
ZenHive mpp
  • affected>= 0.3.0 and < 0.6.3
  • affected>= 65b9e425ce27631c786a5b380b5e4c5ae607ec6d and < ecc038088b1cda09ad8a84acc6cc112addb4a68f

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free