How severe is GHSA-8x4m-qw58-3pcx?

No CVSS score has been assigned to GHSA-8x4m-qw58-3pcx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-8x4m-qw58-3pcx?

GHSA-8x4m-qw58-3pcx affects the following packages: mppx (npm). Ecosystems affected: npm.

How do I fix GHSA-8x4m-qw58-3pcx?

Update mppx to 0.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8x4m-qw58-3pcx is resolved across your whole dependency graph.

How do I detect GHSA-8x4m-qw58-3pcx in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mppx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-8x4m-qw58-3pcx if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-8x4m-qw58-3pcx actively exploited in the wild?

No public exploit code has been indexed for GHSA-8x4m-qw58-3pcx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-8x4m-qw58-3pcx published, and has it been updated?

GHSA-8x4m-qw58-3pcx was published on March 29, 2026 and was last updated on March 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

mppx has multiple payment bypass and griefing vulnerabilitiesGHSA-8x4m-qw58-3pcx

GHSA-8x4m-qw58-3pcx is a security vulnerability in mppx. A fix is available for mppx — see the affected versions and patch details below.

Published

Mar 29, 2026

Updated

Mar 29, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Mar 29, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

142other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

mppxnpm

449Kdownloads / week

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`mppx`	all versions	0.4.8`npm install mppx@0.4.8`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mppx, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update mppx to 0.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8x4m-qw58-3pcx is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is GHSA-8x4m-qw58-3pcx in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works