CVE-2026-87119: ZenHive mpp · Authentication Bypass by Capture-replay
Affects ZenHive mppSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 0.16.2 soon.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.16.2, 4b6eaec02af0e8485cfb4ff68f467d075ed5dd6f
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 22 Sep 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 5 Nov 2026.
What to do
Upgrade mpp to 0.16.2; mpp to 4b6eaec02af0e8485cfb4ff68f467d075ed5dd6f.
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, avoid using affected versions or restrict access to subscription activation credentials to prevent capture and replay.
Description
Authentication Bypass by Capture-replay in ZenHive mpp allows an attacker holding a captured subscription activation credential to charge the payer repeatedly. The payer signs a Tempo KeyAuthorization over the chain id, key type, key id, expiry, limits and scopes only, with nothing tying it to the challenge that prompted it. MPP.Methods.Tempo.KeyAuthorization.verify/3 in lib/mpp/methods/tempo/key_authorization.ex pins each of those signed fields against the subscription request, and the access key it pins is a static per-endpoint server key, so one signed authorization verifies against every challenge the server issues for the same subscription terms. MPP.Methods.Tempo.Subscription.activate/4 deduplicates activations by challenge id, so presenting the captured credential under a fresh challenge produces a different dedup key, claim_activation succeeds, and the subscription transaction is built and broadcast again. Each replay charges the payer's wallet a new first-period settlement and re-authorizes the server key, bounded only by the subscription expiry and the chain's own semantics for re-installing an existing key. This issue affects mpp: from 0.14.0 before 0.16.2.
References
- github.com/ZenHive/mpp/security/advisories/GHSA-p9fv-9w58-95x2 (opens in a new tab)
- cna.erlef.org/cves/CVE-2026-87119.html (opens in a new tab)
- osv.dev/vulnerability/EEF-CVE-2026-87119 (opens in a new tab)
- github.com/ZenHive/mpp/commit/db464dfa9a86ccda58f0827101f6da6bd8aafa78 (opens in a new tab)
- github.com/ZenHive/mpp/commit/4b6eaec02af0e8485cfb4ff68f467d075ed5dd6f (opens in a new tab)