Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-73136 – Authentication Bypass via Replay – ZenHive mpp (Erlang) 0.6.1–0.6.3

Be the first to know when new zero-days emerge:

Summary

CVE-2026-73136 is an authentication bypass (replay) vulnerability in ZenHive’s mpp library (Elixir implementation of the Machine Payments Protocol, HTTP 402 payment middleware), affecting the Tempo payment method module. When a deployment configures a static memo value for Tempo, the library skips its normal per-challenge attribution binding, allowing an attacker to replay a legitimate, publicly visible blockchain transaction hash to gain unauthorized access to paid resources. The issue is rated HIGH severity (CVSS 8.2).

Technical details

  • Root cause: The Elixir.MPP.Methods.Tempo module’s verify/2 and validate_config!/1 functions allow a static memo to be configured instead of the default per-challenge memo. With a static memo, verification only checks token, recipient, amount, and the (non-secret) static memo.
  • Trigger conditions: The vulnerability only manifests when the operator has explicitly configured a static memo in Tempo’s method settings; deployments using the default per-challenge attribution memo are not affected.
  • Attack vector: The static memo is echoed verbatim in unauthenticated responses, and Tempo transfers are recorded on a public blockchain. An attacker can pull a historical, legitimate transfer’s transaction hash/memo from a public block explorer, obtain a fresh authentication challenge, and replay the old transaction to satisfy verification without having made a payment themselves.
  • Impact: Unauthorized access to paid/gated resources. Without a deduplication store, replay is unlimited; even with a deduplication store (e.g., MPP.Tempo.ConCacheStore) configured, the attack degrades to a front-running/race-condition scenario rather than being fully eliminated.
  • Weakness classification: CWE-294 (Authentication Bypass by Capture-replay) and CWE-345 (Insufficient Verification of Data Authenticity).

Affected software

  • Product: mpp (Erlang/Elixir ecosystem package, ZenHive)
  • Affected versions: 0.6.1 through 0.6.3
  • Fixed version: 0.6.4
  • Affected component: lib/mpp/methods/tempo.ex — only relevant when the Tempo method is configured with a static memo value.

Severity

  • CVSS Score: 8.2 (High)
  • CVSS v4.0 Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade mpp to version 0.6.4 or later, which restores proper per-challenge attribution binding checks.
  • If patching is not immediately possible:
    • Remove/disable the static memo configuration for the Tempo method so the system reverts to default per-challenge attribution binding (fully mitigates the issue).
    • If a static memo must be retained, deploy a deduplication store (e.g., MPP.Tempo.ConCacheStore) with a TTL matching the challenge expiry window. This does not fully close the gap but reduces exposure from unlimited replay to a narrow, hash-based race condition window.
  • Review logs/transaction history for repeated use of the same transfer memo/hash across multiple authentication challenges, which may indicate exploitation attempts.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge