{"answers":{"affected":"1 open source package ship an affected version, including mpp.","exploited":"There is no known exploitation of CVE-2026-88255 in the wild and no public exploit code.","fix":"Upgrade mpp to 0.16.2 or later.","what":"CVE-2026-88255 is a medium-severity vulnerability in ZenHive mpp, published on 16 Sep 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-88255 and fix it if it is affected.\n\nWhat it is: CVE-2026-88255 is a medium-severity vulnerability in ZenHive mpp, published on 16 Sep 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-88255 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.16.2\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-88255/ (Markdown: https://insights.sbomify.com/CVE-2026-88255/index.md)","id":"CVE-2026-88255","markdown":"https://insights.sbomify.com/CVE-2026-88255/index.md","name":"CVE-2026-88255","record":{"aliases":["EEF-CVE-2026-88255","GHSA-8x7x-5j8g-8hcx","GHSA-p7v4-jpp9-2m3q"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir payment library","requires_auth":"none","summary":"Attackers can bypass duplicate submission checks by re-encoding transactions, potentially generating multiple valid receipts for a single payment.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"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-1289","name":"Improper Validation of Unsafe Equivalence in Input"}],"description":"Improper Validation of Unsafe Equivalence in Input in ZenHive mpp allows an unauthenticated remote client to pass the Tempo duplicate-submission gate twice with one signed transaction.\n\nMPP.Methods.Tempo reserves the pre-broadcast dedup slot on the caller-supplied hex in reserve_hash_atomic/2, keyed through store_key/1 on tx.raw rather than on a canonical form of the transaction. The deserializer stores the caller's hex verbatim and accepts both recovery-id encodings, so one signed transaction submitted once with v=27 and once with v=0 yields two distinct reserve keys, and both pass the reserve and reach the broadcast path. The plug-level credential replay store is deliberately carved out for tempo in lib/mpp/replay.ex, leaving this reserve as the only gate, and the post-broadcast mark writes the canonical hash key that the raw-keyed reserve never reads.\n\nWhat the duplicate submission yields depends on the node: a nonce-reuse rejection fails closed, while a node that answers with the canonical hash for an already-known transaction returns a second valid Payment-Receipt for a single on-chain payment.\n\nThis issue affects mpp: from 0.2.0 before 0.16.2.","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":"Business logic in mpp","id":"CVE-2026-88255","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":1,"n_references":5,"next":{"headline":"beam_mcp: nested tool argument constraints advertised but not enforced","id":"CVE-2026-88257"},"packages":[{"ecosystem":"Hex","fixed":["0.16.2"],"introduced":["0.2.0"],"last_affected":[],"package":"mpp","purl":"pkg:hex/mpp","source":"EEF-CVE-2026-88255"}],"prev":{"headline":"Sssd: sssd: denial of service via responder connection retry loop during file descriptor exhaustion","id":"CVE-2026-88252"},"products":["mpp"],"published":"2026-09-16","related":[],"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":"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-09-16","vendors":["ZenHive"]},"summary":"Attackers can bypass duplicate submission checks by re-encoding transactions, potentially generating multiple valid receipts for a single payment.","url":"https://insights.sbomify.com/CVE-2026-88255/"}