GHSA-8x4m-qw58-3pcx: Mppx Mppx Has Multiple Payment Bypass Vulnerability

CRITICAL
Share
CWE-294 CWE-345 CWE-288
Published
Advisory Summary

GHSA-8x4m-qw58-3pcx is a CRITICAL mppx has multiple payment bypass vulnerability (CWE-294: Authentication Bypass by Capture-replay) affecting Mppx libraries in the npm ecosystem. The issue involves mppx has multiple payment bypass and griefing vulnerabilities. Remediation is available by upgrading affected packages to version 0.4.8.

GHSA-8x4m-qw58-3pcx at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-8x4m-qw58-3pcx
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-294: Authentication Bypass by Capture-replay
Affected Product Mppx
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-8x4m-qw58-3pcx

To remediate this vulnerability, upgrade all affected Mppx dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

mppx fixed: 0.4.8 
npm install mppx@0.4.8
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls mppx

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-8x4m-qw58-3pcx, inspect your project dependencies using npm:

npm ls mppx

Analyze the terminal output to locate any version of Mppx in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.4.8), your application is affected.

Note: The npm ls mppx command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-294: Authentication Bypass by Capture-replay, where a capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes). In Mppx, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Multiple vulnerabilities were discovered in `tempo/charge` and `tempo/session` which allowed for undesirable behaviors, including: - Replaying `tempo/charge` transaction hashes across push/pull modes, across charge/session endpoints, and via concurrent requests - Performing free `tempo/charge` requests due to missing transfer log verification in pull-mode - Replaying `tempo/charge` credentials across routes via cross-route scope confusion (`memo`/`splits` not included in scope binding) - Manipulating the fee payer of a `tempo/charge` handler into paying for requests (missing sender signature before co-signing) - Bypassing `tempo/session` voucher signature verification - Piggybacking off existing `tempo/session` channels via settle voucher reuse and weak channel ID binding - Performing free `tempo/session` requests by exploiting channel reopen without on-chain settled state - Accepting deductions on finalized `tempo/session` channels - Bypassing payment on free routes via method-mismatch fallback - Griefing `tempo/session` channels via force-close detection bypass (`closeRequestedAt` not persisted) ### Patches Fixed in 0.4.8. ### Workarounds There are no workarounds available for these vulnerabilities.

GHSA-8x4m-qw58-3pcx Affected Mppx Versions

1 component(s)
Fixed Versions:
0.4.8
Product / Package Ecosystem Affected Versions Fixed Version
mppx
npm/mppx
npm
< 0.4.8
0.4.8

References

GitHub Advisory / Wiki ADVISORY
https://github.com/wevm/mppx/security/advisories/GHSA-8x4m-qw58-3pcx
Mppx Source Repository REPOSITORY
https://github.com/wevm/mppx

Frequently Asked Questions

What is GHSA-8x4m-qw58-3pcx?
GHSA-8x4m-qw58-3pcx is a security vulnerability in Mppx involving mppx has multiple payment bypass and griefing vulnerabilities under CWE-294: Authentication Bypass by Capture-replay.
Which Mppx versions are affected?
Affected versions include releases prior to 0.4.8 across affected packages: mppx.
What version fixes GHSA-8x4m-qw58-3pcx?
Upgrading to 0.4.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is mppx affected?
Yes, mppx is affected in releases prior to 0.4.8. Upgrade your dependency to 0.4.8 or later.
What CWE is associated with GHSA-8x4m-qw58-3pcx?
GHSA-8x4m-qw58-3pcx is classified under CWE-294: Authentication Bypass by Capture-replay (A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).).
How can I check npm dependencies for GHSA-8x4m-qw58-3pcx?
Run the dependency tree command: 'npm ls mppx'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-8x4m-qw58-3pcx",
  "modified" : "2026-03-29T15:15:36Z",
  "published" : "2026-03-29T15:15:36Z",
  "aliases" : [ ],
  "summary" : "mppx has multiple payment bypass and griefing vulnerabilities",
  "details" : "### Impact\n\nMultiple vulnerabilities were discovered in `tempo/charge` and `tempo/session` which allowed for undesirable behaviors, including:\n- Replaying `tempo/charge` transaction hashes across push/pull modes, across charge/session endpoints, and via concurrent requests\n- Performing free `tempo/charge` requests due to missing transfer log verification in pull-mode\n- Replaying `tempo/charge` credentials across routes via cross-route scope confusion (`memo`/`splits` not included in scope binding)\n- Manipulating the fee payer of a `tempo/charge` handler into paying for requests (missing sender signature before co-signing)\n- Bypassing `tempo/session` voucher signature verification\n- Piggybacking off existing `tempo/session` channels via settle voucher reuse and weak channel ID binding\n- Performing free `tempo/session` requests by exploiting channel reopen without on-chain settled state\n- Accepting deductions on finalized `tempo/session` channels\n- Bypassing payment on free routes via method-mismatch fallback\n- Griefing `tempo/session` channels via force-close detection bypass (`closeRequestedAt` not persisted)\n\n### Patches\n\nFixed in 0.4.8.\n\n### Workarounds\n\nThere are no workarounds available for these vulnerabilities.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "mppx"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.4.8"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/wevm/mppx/security/advisories/GHSA-8x4m-qw58-3pcx"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/wevm/mppx"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-288", "CWE-294", "CWE-345" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-29T15:15:36Z",
    "nvd_published_at" : null
  }
}