{"answers":{"affected":"2 open source packages ship an affected version, including mppx.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63628 exists.","fix":"Upgrade mppx to 0.8.2 or later.","what":"CVE-2026-63628 is a medium-severity denial of service vulnerability in wevm mppx, published on 22 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-63628 and fix it if it is affected.\n\nWhat it is: CVE-2026-63628 is a medium-severity denial of service vulnerability in wevm mppx, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-63628 exists.\n\nAffected packages and fixed versions:\n- mppx (npm): affected all versions; fixed in 0.8.2\n- mppx (npm): affected all versions; fixed in 0.8.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-63628/ (Markdown: https://insights.sbomify.com/CVE-2026-63628/index.md)","id":"CVE-2026-63628","markdown":"https://insights.sbomify.com/CVE-2026-63628/index.md","name":"CVE-2026-63628","record":{"aliases":["GHSA-vc9j-9wph-qghj"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"TypeScript payment library","requires_auth":"none","summary":"Attackers can inflate transaction fees for the fee-payer wallet by injecting fabricated access-list entries, causing financial denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"mppx is a TypeScript interface for machine payments protocol. Prior to 0.8.2, the fee-payer cosigning path in src/tempo/internal/fee-payer.ts copied a client-supplied access_list from a 0x78 FeePayerEnvelope without validating its length or contents. Because EIP-2930 access-list entries consume intrinsic gas even when the listed addresses are never used, a client could add fabricated address-only entries and cause the server fee_payer wallet to pay unnecessary transaction fees. The demonstrated 180-entry list remained within the 500,000 gas policy cap, 16 KB header limit, and RPC simulation budget while increasing the fee by approximately 9.4 times. This issue is fixed in version 0.8.2.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"mppx: Gas Draining with access list","id":"CVE-2026-63628","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"BentoPDF: Workflow Import Allows Unvalidated TSA URL Leading to PDF Hash Exfiltration via RFC 3161 Requests","id":"CVE-2026-63630"},"packages":[{"ecosystem":"npm","fixed":["0.8.2"],"introduced":["0"],"last_affected":[],"package":"mppx","purl":null,"source":"GHSA-vc9j-9wph-qghj"},{"ecosystem":"npm","fixed":["0.8.2"],"introduced":["0"],"last_affected":[],"package":"mppx","purl":"pkg:npm/mppx","source":"GHSA-vc9j-9wph-qghj"}],"prev":{"headline":"mppx: Gas Draining with padding","id":"CVE-2026-63627"},"products":["mppx"],"published":"2026-09-22","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["wevm"]},"summary":"Attackers can inflate transaction fees for the fee-payer wallet by injecting fabricated access-list entries, causing financial denial of service.","url":"https://insights.sbomify.com/CVE-2026-63628/"}