https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T01:34:01.632186+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-278346 EUVD-2026-278346 2026-10-06T01:34:01.698027+00:00 EUVD-2026-278346 https://cve.radiocsirt.org/vuln/fkie_cve-2026-34210 fkie_cve-2026-34210 2026-10-06T01:34:01.698070+00:00

mppx is a TypeScript interface for machine payments protocol. Prior to version 0.4.11, the 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. This issue has been patched in version 0.4.11.

 https://cve.radiocsirt.org/vuln/ghsa-8mhj-rffc-rcvw GHSA-8mhj-rffc-rcvw — mppx has Stripe charge credential replay via missing idempotency check 2026-10-06T01:34:01.698109+00:00

Affected: npm: mppx

### Impact

The `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.

### Patches

Fixed in 0.4.11. The server now checks the `Idempotent-Replayed` header and rejects replayed PaymentIntents.

### Workarounds

There are no workarounds available for this vulnerability.