{"answers":{"affected":"2 open source packages ship an affected version, including mppx. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34210 in the wild and no public exploit code.","fix":"Upgrade mppx to 0.4.11 or later.","what":"CVE-2026-34210 is a medium-severity vulnerability in wevm mppx, published on 31 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34210 and fix it if it is affected.\n\nWhat it is: CVE-2026-34210 is a medium-severity vulnerability in wevm mppx, published on 31 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 CVE-2026-34210 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mppx (npm): affected all versions; fixed in 0.4.11\n- mppx (npm): affected all versions; fixed in 0.4.11\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/CVE-2026-34210/ (Markdown: https://insights.sbomify.com/CVE-2026-34210/index.md)","id":"CVE-2026-34210","markdown":"https://insights.sbomify.com/CVE-2026-34210/index.md","name":"CVE-2026-34210","record":{"aliases":["GHSA-8mhj-rffc-rcvw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"TypeScript payment library","requires_auth":"low_privilege","summary":"Attackers can replay payment credentials to consume unlimited resources without paying, affecting users of the mppx TypeScript library.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mppx","vendor":"wevm"}],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-697","name":"Incorrect Comparison"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"mppx has Stripe charge credential replay via missing idempotency check","id":"CVE-2026-34210","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"SandboxJS: Stack overflow DoS via deeply nested expressions in recursive descent parser","id":"CVE-2026-34211"},"packages":[{"ecosystem":"npm","fixed":["0.4.11"],"introduced":["0"],"last_affected":[],"package":"mppx","purl":null,"source":"GHSA-8mhj-rffc-rcvw"},{"ecosystem":"npm","fixed":["0.4.11"],"introduced":["0"],"last_affected":[],"package":"mppx","purl":"pkg:npm/mppx","source":"GHSA-8mhj-rffc-rcvw"}],"prev":{"headline":"mppx: Tempo has a session close voucher bypass vulnerability due to settled amount equality","id":"CVE-2026-34209"},"products":["mppx"],"published":"2026-03-31","related":[{"cvss_score":7.5,"headline":"mppx: Tempo has a session close voucher bypass vulnerability due to settled amount equality","id":"CVE-2026-34209","kev_date_added":null,"published":"2026-03-31"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-31","vendors":["wevm"]},"summary":"Attackers can replay payment credentials to consume unlimited resources without paying, affecting users of the mppx TypeScript library.","url":"https://insights.sbomify.com/CVE-2026-34210/"}