CVE-2026-87119

mpp Tempo subscription key authorization is not bound to the issuing challenge, allowing a captured activation credential to be replayed

HIGH
8.2
CVSS Score
Published: September 22, 2026 at 11:16 AM UTC
Updated: September 22, 2026 at 07:21 PM UTC
1 product affected across 1 vendorMachine Payments Protocol

Using mpp by ZenHive?

Get instant alerts when new vulnerabilities affect mpp - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.2
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0.14.0 ≤ v < 0.16.20.14.0db464dfa9a86ccda58f0827101f6da6bd8aafa78
Vendor states this is fixed in 4b6eaec02af0e8485cfb4ff68f467d075ed5dd6f (fixed)
Affected range stops below 0.16.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.2HIGHEEF
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-294

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card