Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-mv9j-8jvg-j8mr | mppx: Tempo has a session close voucher bypass vulnerability due to settled amount equality |
Fri, 03 Apr 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:wevm:mppx:*:*:*:*:*:node.js:*:* |
Thu, 02 Apr 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 01 Apr 2026 02:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wevm
Wevm mppx |
|
| Vendors & Products |
Wevm
Wevm mppx |
Tue, 31 Mar 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | mppx is a TypeScript interface for machine payments protocol. Prior to version 0.4.11, the tempo/session cooperative close handler validated the close voucher amount using "<" instead of "<=" against the on-chain settled amount. An attacker could submit a close voucher exactly equal to the settled amount, which would be accepted without committing any new funds, effectively closing or griefing the channel for free. This issue has been patched in version 0.4.11. | |
| Title | mppx: Tempo has a session close voucher bypass vulnerability due to settled amount equality | |
| Weaknesses | CWE-294 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-02T15:13:32.047Z
Reserved: 2026-03-26T15:57:52.324Z
Link: CVE-2026-34209
Updated: 2026-04-02T15:13:26.917Z
Status : Analyzed
Published: 2026-03-31T15:16:18.030
Modified: 2026-04-03T15:59:37.143
Link: CVE-2026-34209
No data.
OpenCVE Enrichment
Updated: 2026-04-03T21:17:43Z
Github GHSA