{"answers":{"affected":"2 open source packages ship an affected version, including mppx.","exploited":"There is no known exploitation of GHSA-8x4m-qw58-3pcx in the wild and no public exploit code.","fix":"Upgrade mppx to 0.4.8 or later.","what":"GHSA-8x4m-qw58-3pcx is a vulnerability in mppx, published on 29 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-8x4m-qw58-3pcx and fix it if it is affected.\n\nWhat it is: GHSA-8x4m-qw58-3pcx is a vulnerability in mppx, published on 29 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-8x4m-qw58-3pcx in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mppx (npm): affected all versions; fixed in 0.4.8\n- mppx (npm): affected all versions; fixed in 0.4.8\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-8x4m-qw58-3pcx/ (Markdown: https://insights.sbomify.com/GHSA-8x4m-qw58-3pcx/index.md)","id":"GHSA-8x4m-qw58-3pcx","markdown":"https://insights.sbomify.com/GHSA-8x4m-qw58-3pcx/index.md","name":"GHSA-8x4m-qw58-3pcx","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"npm payment library","requires_auth":"low_privilege","summary":"Attackers can bypass payment verification and manipulate session channels in the mppx library, leading to financial loss and service disruption.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nMultiple vulnerabilities were discovered in `tempo/charge` and `tempo/session` which allowed for undesirable behaviors, including:\n- Replaying `tempo/charge` transaction hashes across push/pull modes, across charge/session endpoints, and via concurrent requests\n- Performing free `tempo/charge` requests due to missing transfer log verification in pull-mode\n- Replaying `tempo/charge` credentials across routes via cross-route scope confusion (`memo`/`splits` not included in scope binding)\n- Manipulating the fee payer of a `tempo/charge` handler into paying for requests (missing sender signature before co-signing)\n- Bypassing `tempo/session` voucher signature verification\n- Piggybacking off existing `tempo/session` channels via settle voucher reuse and weak channel ID binding\n- Performing free `tempo/session` requests by exploiting channel reopen without on-chain settled state\n- Accepting deductions on finalized `tempo/session` channels\n- Bypassing payment on free routes via method-mismatch fallback\n- Griefing `tempo/session` channels via force-close detection bypass (`closeRequestedAt` not persisted)\n\n### Patches\n\nFixed in 0.4.8.\n\n### Workarounds\n\nThere are no workarounds available for these vulnerabilities.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"mppx has multiple payment bypass and griefing vulnerabilities","id":"GHSA-8x4m-qw58-3pcx","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["0.4.8"],"introduced":["0"],"last_affected":[],"package":"mppx","purl":null,"source":"GHSA-8x4m-qw58-3pcx"},{"ecosystem":"npm","fixed":["0.4.8"],"introduced":["0"],"last_affected":[],"package":"mppx","purl":"pkg:npm/mppx","source":"GHSA-8x4m-qw58-3pcx"}],"products":null,"published":"2026-03-29","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can bypass payment verification and manipulate session channels in the mppx library, leading to financial loss and service disruption.","url":"https://insights.sbomify.com/GHSA-8x4m-qw58-3pcx/"}