Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

GHSA-fxc9-7j2w-vx54 — mpp

GHSA-fxc9-7j2w-vx54 is a security vulnerability in mpp. A fix is available for mpp — see the affected versions and patch details below.

mpp has multiple payment bypass and griefing vulnerabilities

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
🦀mpp

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Multiple vulnerabilities were discovered which allowed for undesirable behaviors, including:

  • Performing free tempo/charge requests
  • Replaying existing tempo/charge requests
  • Performing free tempo/session requests
  • Piggybacking off existing tempo/session channels
  • Griefing existing tempo/session channels
  • Manipulate the fee payer of a tempo/charge or tempo/session handler into paying for requests
  • Replaying existing stripe/charge requests

Patches

The issues are patched in 0.8.0

Workarounds

There are no workarounds available for these vulnerabilities

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iomppall versions0.8.0cargo update -p mpp --precise 0.8.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update mpp to 0.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fxc9-7j2w-vx54 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fxc9-7j2w-vx54 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-fxc9-7j2w-vx54. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Multiple vulnerabilities were discovered which allowed for undesirable behaviors, including: - Performing free `tempo/charge` requests - Replaying existing `tempo/charge` requests - Performing free `tempo/session` requests - Piggybacking off existing `tempo/session` channels - Griefing existing `tempo/session` channels - Manipulate the fee payer of a `tempo/charge` or `tempo/session` handler into paying for requests - Replaying existing `stripe/charge` requests ### Patches The issues are patched in 0.8.0 ### Workarounds There are no workarounds available for these vulnerabilities
O3 Security · Impact-Aware SCA

Is GHSA-fxc9-7j2w-vx54 in your dependencies?

O3 Security finds GHSA-fxc9-7j2w-vx54 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-fxc9-7j2w-vx54: mpp | O3 Security