Skip to content

Commit 859baab

Browse files
1 parent 45c28f1 commit 859baab

2 files changed

Lines changed: 130 additions & 0 deletions

File tree

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-8mhj-rffc-rcvw",
4+
"modified": "2026-03-29T15:11:30Z",
5+
"published": "2026-03-29T15:11:30Z",
6+
"aliases": [
7+
"CVE-2026-34210"
8+
],
9+
"summary": "mppx has Stripe charge credential replay via missing idempotency check",
10+
"details": "### Impact\n\nThe `stripe/charge` payment method did not check Stripe's `Idempotent-Replayed` response header when creating PaymentIntents. An attacker could replay a valid credential containing the same `spt` token against a new challenge, and the server would accept the replayed Stripe PaymentIntent as a new successful payment without actually charging the customer again. This allowed an attacker to pay once and consume unlimited resources by replaying the credential.\n\n### Patches\n\nFixed in 0.4.11. The server now checks the `Idempotent-Replayed` header and rejects replayed PaymentIntents.\n\n### Workarounds\n\nThere are no workarounds available for this vulnerability.",
11+
"severity": [
12+
{
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "npm",
21+
"name": "mppx"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "0"
29+
},
30+
{
31+
"fixed": "0.4.11"
32+
}
33+
]
34+
}
35+
]
36+
}
37+
],
38+
"references": [
39+
{
40+
"type": "WEB",
41+
"url": "https://github.com/wevm/mppx/security/advisories/GHSA-8mhj-rffc-rcvw"
42+
},
43+
{
44+
"type": "WEB",
45+
"url": "https://github.com/wevm/mppx/commit/b2b1a0b60506fc71aa80b8a025084949dca1a994"
46+
},
47+
{
48+
"type": "PACKAGE",
49+
"url": "https://github.com/wevm/mppx"
50+
},
51+
{
52+
"type": "WEB",
53+
"url": "https://github.com/wevm/mppx/releases/tag/mppx%400.4.11"
54+
}
55+
],
56+
"database_specific": {
57+
"cwe_ids": [
58+
"CWE-697"
59+
],
60+
"severity": "MODERATE",
61+
"github_reviewed": true,
62+
"github_reviewed_at": "2026-03-29T15:11:30Z",
63+
"nvd_published_at": null
64+
}
65+
}
Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-mv9j-8jvg-j8mr",
4+
"modified": "2026-03-29T15:10:03Z",
5+
"published": "2026-03-29T15:10:03Z",
6+
"aliases": [
7+
"CVE-2026-34209"
8+
],
9+
"summary": "mppx: Tempo has a session close voucher bypass vulnerability due to settled amount equality",
10+
"details": "### Impact\n\nThe `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.\n\n### Patches\n\nFixed in 0.4.11.\n\n### Workarounds\n\nThere are no workarounds available for this vulnerability.",
11+
"severity": [
12+
{
13+
"type": "CVSS_V3",
14+
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "npm",
21+
"name": "mppx"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "0"
29+
},
30+
{
31+
"fixed": "0.4.11"
32+
}
33+
]
34+
}
35+
]
36+
}
37+
],
38+
"references": [
39+
{
40+
"type": "WEB",
41+
"url": "https://github.com/wevm/mppx/security/advisories/GHSA-mv9j-8jvg-j8mr"
42+
},
43+
{
44+
"type": "WEB",
45+
"url": "https://github.com/wevm/mppx/commit/94088246ee18f21b5d6be40d9e7a464f5a280bfb"
46+
},
47+
{
48+
"type": "PACKAGE",
49+
"url": "https://github.com/wevm/mppx"
50+
},
51+
{
52+
"type": "WEB",
53+
"url": "https://github.com/wevm/mppx/releases/tag/mppx@0.4.11"
54+
}
55+
],
56+
"database_specific": {
57+
"cwe_ids": [
58+
"CWE-294"
59+
],
60+
"severity": "HIGH",
61+
"github_reviewed": true,
62+
"github_reviewed_at": "2026-03-29T15:10:03Z",
63+
"nvd_published_at": null
64+
}
65+
}

0 commit comments

Comments
 (0)