GHSA-8x4m-qw58-3pcx mppx has multiple payment bypass and griefing vulnerabilities
Not scored
Published
Check this codebase for GHSA-8x4m-qw58-3pcx and fix it if it is affected.
What it is: GHSA-8x4m-qw58-3pcx is a vulnerability in mppx, published on 29 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-8x4m-qw58-3pcx in the wild and no public exploit code.
Affected packages and fixed versions:
- mppx (npm): affected all versions; fixed in 0.4.8
- mppx (npm): affected all versions; fixed in 0.4.8
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/GHSA-8x4m-qw58-3pcx/ (Markdown: https://insights.sbomify.com/GHSA-8x4m-qw58-3pcx/index.md)
Attackers can bypass payment verification and manipulate session channels in the mppx library, leading to financial loss and service disruption.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-8x4m-qw58-3pcx?
GHSA-8x4m-qw58-3pcx is a vulnerability in mppx, published on 29 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Impact
Multiple vulnerabilities were discovered in tempo/charge and tempo/session which allowed for undesirable behaviors, including:
- Replaying
tempo/chargetransaction hashes across push/pull modes, across charge/session endpoints, and via concurrent requests - Performing free
tempo/chargerequests due to missing transfer log verification in pull-mode - Replaying
tempo/chargecredentials across routes via cross-route scope confusion (memo/splitsnot included in scope binding) - Manipulating the fee payer of a
tempo/chargehandler into paying for requests (missing sender signature before co-signing) - Bypassing
tempo/sessionvoucher signature verification - Piggybacking off existing
tempo/sessionchannels via settle voucher reuse and weak channel ID binding - Performing free
tempo/sessionrequests by exploiting channel reopen without on-chain settled state - Accepting deductions on finalized
tempo/sessionchannels - Bypassing payment on free routes via method-mismatch fallback
- Griefing
tempo/sessionchannels via force-close detection bypass (closeRequestedAtnot persisted)
Patches
Fixed in 0.4.8.
Workarounds
There are no workarounds available for these vulnerabilities.
Which versions are affected by GHSA-8x4m-qw58-3pcx?
2 open source packages ship an affected version, including mppx.
| Package | Affected | Fixed in |
|---|---|---|
mppx npm | All versions | 0.4.8 |
mppx npm | All versions | 0.4.8 |
How do I fix GHSA-8x4m-qw58-3pcx?
Upgrade mppx to 0.4.8 or later.
Is GHSA-8x4m-qw58-3pcx being exploited?
There is no known exploitation of GHSA-8x4m-qw58-3pcx in the wild and no public exploit code.