{"answers":{"affected":"2 open source packages ship an affected version, including vm2.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47683 exists.","fix":"Upgrade vm2 to 3.11.6 or later.","what":"CVE-2026-47683 is a high-severity denial of service vulnerability in patriksimek vm2, published on 17 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-47683 and fix it if it is affected.\n\nWhat it is: CVE-2026-47683 is a high-severity denial of service vulnerability in patriksimek vm2, published on 17 Aug 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-47683 exists.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected all versions; fixed in 3.11.6\n- vm2 (npm): affected all versions; fixed in 3.11.6\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-47683/ (Markdown: https://insights.sbomify.com/CVE-2026-47683/index.md)","id":"CVE-2026-47683","markdown":"https://insights.sbomify.com/CVE-2026-47683/index.md","name":"CVE-2026-47683","record":{"aliases":["CLEANSTART-2026-MK88618","ECHO-a5bc-78ae-239f","GHSA-gmc2-2x9w-cgh9","MINI-pcj6-6944-24f3","ROOT-APP-NPM-CVE-2026-47683"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js sandbox library","requires_auth":"none","summary":"Sandboxed code can bypass memory limits via Buffer operations, causing host process exhaustion and 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":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.6, the bufferAllocLimit enforcement in lib/setup-sandbox.js does not cover Buffer.concat(list, totalLength) or Buffer.from(arrayLike) with an attacker-controlled length, allowing sandbox code to perform large synchronous host external-memory allocations that bypass the configured cap and can exhaust the host process. This issue is fixed in version 3.11.6.","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":"vm2: bufferAllocLimit cap bypassed by Buffer.concat and Buffer.from arrayLike","id":"CVE-2026-47683","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Sync-in Server: SSRF protection bypass via IPv4-mapped IPv6 addresses in regExpPrivateIP","id":"CVE-2026-47684"},"packages":[{"ecosystem":"npm","fixed":["3.11.6"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-gmc2-2x9w-cgh9"},{"ecosystem":"npm","fixed":["3.11.6"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-gmc2-2x9w-cgh9"}],"prev":{"headline":"CVAT: Missing path-containment validation in multiple entry points allows arbitrary path writes","id":"CVE-2026-47682"},"products":["vm2"],"published":"2026-08-17","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":"total"},"state":"PUBLISHED","updated":"2026-08-18","vendors":["patriksimek"]},"summary":"Sandboxed code can bypass memory limits via Buffer operations, causing host process exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-47683/"}