Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3amended

mppx has multiple payment bypass and griefing vulnerabilities

GHSA-8x4m-qw58-3pcx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (mppx 0.4.8), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm mppx

    Affected
    < 0.4.8
    Fixed in
    0.4.8

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.3 · 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 · score source
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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 -…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-8x4m-qw58-3pcx

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-8x4m-qw58-3pcx

  4. Revision 1 · created ·

    Published from ghsa record GHSA-8x4m-qw58-3pcx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-8x4m-qw58-3pcx

Advisory: mppx has multiple payment bypass and griefing vulnerabilities
IDs: GHSA-8x4m-qw58-3pcx
Record: https://patchnext.com/advisories/ghsa-8x4m-qw58-3pcx (revision 4, source checked 26 Oct 2026, 12:47 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mppx 0.4.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm mppx: affected < 0.4.8; fixed in 0.4.8

## Suggested inspection (read-only)
- `npm ls mppx --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mppx.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8x4m-qw58-3pcx (GitHub-reviewed advisory GHSA-8x4m-qw58-3pcx lists affected ranges: npm mppx >=0 <0.4.8)
- Verified: https://osv.dev/vulnerability/GHSA-8x4m-qw58-3pcx (OSV record GHSA-8x4m-qw58-3pcx lists affected ranges: npm mppx >=0 <0.4.8 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…