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

New CVE Detected

CVE-2026-67581 – Authentication Bypass via Payment Replay – ZenHive mpp 0.3.0–0.6.2

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

Summary

CVE-2026-67581 is a high-severity authentication bypass / payment-verification flaw in ZenHive’s mpp Elixir package (an implementation of the Machine Payments Protocol used as HTTP 402 payment middleware for AI agents and machine-to-machine commerce). The MPP.Methods.EVM.verify/2 function fails to enforce single-use semantics on on-chain transfer proofs, allowing a single settled blockchain transaction to be replayed to satisfy an unlimited number of subsequent payment challenges. The issue affects versions 0.3.0 through 0.6.2 and is fixed in 0.6.3.

Technical details

  • Root cause: The EVM payment verification logic validates a submitted transfer proof solely by matching token, to (recipient), and amount fields against historical on-chain transfers. It does not bind the proof to a specific payment challenge, nor does it track/consume the underlying transaction hash once used.
  • Trigger conditions: Because challenge IDs regenerate on every payment request/response cycle, an attacker who has completed (or observed) one valid on-chain transfer matching a given token/recipient/amount combination can resubmit that same transaction as proof against any new challenge with matching parameters — most easily exploited on static-price routes.
  • Attack vector: Network-based, no authentication or user interaction required (AV:N, AC:L, AT:N, PR:N, UI:N), since the affected code path is the public payment-verification endpoint of the middleware.
  • Impact: Attackers can bypass payment enforcement entirely, obtaining unlimited access to paid resources/services gated behind the mpp payment middleware after paying for access only once, resulting in loss of integrity/availability of the payment-gating mechanism (billing bypass / free access to metered resources).

Affected software

  • ZenHive mpp (Erlang/Elixir Hex package), versions 0.3.0 through 0.6.2 (inclusive)
  • Git revisions up to and including commit 65b9e425ce27631c786a5b380b5e4c5ae607ec6d
  • Fixed in version 0.6.3

Severity

  • CVSS v4.0 Base Score: 8.7 (High)
  • Vector: 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

Mitigation and recommended actions

  • Immediate: Upgrade mpp to version 0.6.3 or later. The patched version adds support for an MPP.Tempo.Store dedup store that checks a submitted transaction hash for prior use and atomically marks it consumed after verification, rejecting misconfigured stores at initialization.
  • If unable to patch immediately:
    • Configure per-challenge pricing (e.g., vary the required amount slightly per challenge) so that a previously used transaction cannot satisfy a new charge’s exact token/recipient/amount match.
    • Enforce short challenge expiry windows to reduce the replay window.
    • Consider migrating on-chain payment flows to the Tempo payment method, which is not affected by this weakness.
    • After upgrading to 0.6.3, configure a dedup store with a TTL matching the challenge expiry duration to fully enforce single-use transaction semantics.

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