{"answers":{"affected":"1 open source package ship an affected version, including mpp. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-73829 in the wild and no public exploit code.","fix":"Upgrade mpp to 0.6.1 or later.","what":"CVE-2026-73829 is a medium-severity vulnerability in ZenHive mpp, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-73829 and fix it if it is affected.\n\nWhat it is: CVE-2026-73829 is a medium-severity vulnerability in ZenHive mpp, published on 19 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-73829 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mpp (Hex): affected from 0.2.0; fixed in 0.6.1\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-73829/ (Markdown: https://insights.sbomify.com/CVE-2026-73829/index.md)","id":"CVE-2026-73829","markdown":"https://insights.sbomify.com/CVE-2026-73829/index.md","name":"CVE-2026-73829","record":{"aliases":["EEF-CVE-2026-73829","GHSA-vjfr-ffhr-5g8p","GHSA-w8j7-7qc3-5f24"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Elixir payment library","requires_auth":"none","summary":"Attackers can replay confirmed payments for multiple accesses due to a race condition in the hash credential verification path.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[{"product":"machine_payments_protocol","vendor":"zenhive"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"Time-of-check Time-of-use (TOCTOU) Race Condition in ZenHive mpp allows an unauthenticated remote client to redeem one confirmed on-chain payment for multiple paid-resource accesses.\n\nThe type=\"hash\" credential path in MPP.Methods.Tempo.verify/2 guards against replay with a non-atomic check-then-mark sequence: check_hash_unused/2 reads the dedup store, an eth_getTransactionReceipt round trip verifies the payment on chain, and only then does mark_hash_used/2 write the mark. Concurrent requests carrying the same settled payment hash all pass the read before any of them writes, so each is issued a receipt. The store's atomic check_and_mark/2 primitive is available and used by the type=\"transaction\" path, but the hash path calls plain get and put even when the configured store implements it. Exploitation requires a dedup store to be configured; the default nil store is stateless and documented as offering no replay protection at all.\n\nThis issue affects mpp: from 0.2.0 before 0.6.1.","ecosystems":["Hex"],"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":"Non-atomic hash-credential dedup in mpp Tempo allows replay of a confirmed payment under a concurrent race","id":"CVE-2026-73829","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Must-gather: must-gather: embedded secret data in acm wrapper crs collected without redaction","id":"CVE-2026-73834"},"packages":[{"ecosystem":"Hex","fixed":["0.6.1"],"introduced":["0.2.0"],"last_affected":[],"package":"mpp","purl":"pkg:hex/mpp","source":"EEF-CVE-2026-73829"}],"prev":{"headline":"Cross-site scripting in SOY Calendar","id":"CVE-2026-73827"},"products":["mpp"],"published":"2026-08-19","related":[{"cvss_score":8.7,"headline":"On-chain transfer proof is not single-use in mpp EVM payment method, enabling cross-challenge replay","id":"CVE-2026-67581","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":8.3,"headline":"Denial of service in mpp","id":"CVE-2026-73541","kev_date_added":null,"published":"2026-08-19"},{"cvss_score":8.2,"headline":"Static memo configuration in mpp Tempo disables per-challenge attribution binding, enabling third-party replay","id":"CVE-2026-73136","kev_date_added":null,"published":"2026-08-19"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"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-08-19","vendors":["ZenHive"]},"summary":"Attackers can replay confirmed payments for multiple accesses due to a race condition in the hash credential verification path.","url":"https://insights.sbomify.com/CVE-2026-73829/"}