{"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-73541 in the wild and no public exploit code.","fix":"Upgrade mpp to 0.12.0 or later.","what":"CVE-2026-73541 is a high-severity denial of service 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-73541 and fix it if it is affected.\n\nWhat it is: CVE-2026-73541 is a high-severity denial of service 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-73541 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.12.0\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-73541/ (Markdown: https://insights.sbomify.com/CVE-2026-73541/index.md)","id":"CVE-2026-73541","markdown":"https://insights.sbomify.com/CVE-2026-73541/index.md","name":"CVE-2026-73541","record":{"aliases":["EEF-CVE-2026-73541","GHSA-j4j7-7xpr-c7cr","GHSA-j5gr-9qmc-3234"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir payment library","requires_auth":"none","summary":"An unauthenticated attacker can drain a sponsor wallet via concurrent transactions, causing denial of service for legitimate users.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[{"product":"machine_payments_protocol","vendor":"zenhive"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"Allocation of Resources Without Limits or Throttling in ZenHive mpp allows an unauthenticated remote client to drain the fee-payer wallet through concurrent sponsored payments, denying service to legitimate payers once it is empty.\n\nMPP.Methods.Tempo.FeePayerPolicy enforces its ceilings (max_gas, max_fee_per_gas, max_priority_fee_per_gas, the worst-case gas_limit * max_fee_per_gas \u003c= max_total_fee budget cap, and a validity window) against one transaction at a time, and nothing accounts for exposure across concurrent requests. reserve_hash_atomic/2 is keyed on the transaction hash, so it prevents duplicate broadcast of the same signed transaction but not N distinct sponsored transactions carrying distinct expiring nonces. Committed sponsor exposure is therefore N times max_total_fee, bounded by nothing in the library, and the default 900 second validity window lets co-signed transactions stay broadcastable and uncounted for that entire period.\n\nThis issue affects mpp: from 0.2.0 before 0.12.0.","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":"Denial of service in mpp","id":"CVE-2026-73541","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Weak cryptography in Multiple SEIKO EPSON printers and scanners","id":"CVE-2026-73542"},"packages":[{"ecosystem":"Hex","fixed":["0.12.0"],"introduced":["0.2.0"],"last_affected":[],"package":"mpp","purl":"pkg:hex/mpp","source":"EEF-CVE-2026-73541"}],"prev":{"headline":"Gitea external renderer argument injection and code execution","id":"CVE-2026-73539"},"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.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"},{"cvss_score":6.3,"headline":"Non-atomic hash-credential dedup in mpp Tempo allows replay of a confirmed payment under a concurrent race","id":"CVE-2026-73829","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":"total"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["ZenHive"]},"summary":"An unauthenticated attacker can drain a sponsor wallet via concurrent transactions, causing denial of service for legitimate users.","url":"https://insights.sbomify.com/CVE-2026-73541/"}