{"answers":{"affected":"2 open source packages ship an affected version, including @socket.io/cluster-engine.","exploited":"There is no known exploitation of CVE-2026-102600 in the wild and no public exploit code.","fix":"Upgrade @socket.io/cluster-engine to 0.1.1 or later.","what":"CVE-2026-102600 is a high-severity vulnerability in @socket.io cluster-engine, published on 29 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-102600 and fix it if it is affected.\n\nWhat it is: CVE-2026-102600 is a high-severity vulnerability in @socket.io cluster-engine, published on 29 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-102600 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @socket.io/cluster-engine (npm): affected all versions; fixed in 0.1.1\n- @socket.io/cluster-engine (npm): affected all versions; fixed in 0.1.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-102600/ (Markdown: https://insights.sbomify.com/CVE-2026-102600/index.md)","id":"CVE-2026-102600","markdown":"https://insights.sbomify.com/CVE-2026-102600/index.md","name":"CVE-2026-102600","record":{"aliases":["GHSA-wfpm-5gcm-94cg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Socket.IO cluster engine","requires_auth":"none","summary":"Attacker can crash Node.js process via prototype pollution in clustered Socket.IO deployments, causing denial of service.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"Socket.IO enables bidirectional and low-latency communication for every platform. Prior to 0.1.1, @socket.io/cluster-engine uses inherited object properties when looking up attacker-controlled session IDs in clustered deployments. Special property names such as __proto__ or constructor can resolve through the object prototype chain instead of identifying an actual connected client, causing the Node.js process to crash and resulting in denial of service. Applications that do not use @socket.io/cluster-engine are not affected. This issue is fixed in version 0.1.1.","ecosystems":["npm"],"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":"Socket.IO: Prototype Pollution via Unsafe Client Session Lookup","id":"CVE-2026-102600","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Flysystem: WhitespacePathNormalizer's control-character (CorruptedPathDetected) check is bypassed by malformed UTF-8 in the path, affecting every adapter","id":"CVE-2026-102601"},"packages":[{"ecosystem":"npm","fixed":["0.1.1"],"introduced":["0"],"last_affected":[],"package":"@socket.io/cluster-engine","purl":null,"source":"GHSA-wfpm-5gcm-94cg"},{"ecosystem":"npm","fixed":["0.1.1"],"introduced":["0"],"last_affected":[],"package":"@socket.io/cluster-engine","purl":"pkg:npm/%40socket.io/cluster-engine","source":"GHSA-wfpm-5gcm-94cg"}],"prev":{"headline":"Socket.IO: Engine.IO Protocol Revision Mismatch DoS","id":"CVE-2026-102599"},"products":["cluster-engine","socket.io"],"published":"2026-09-29","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["@socket.io","socketio"]},"summary":"Attacker can crash Node.js process via prototype pollution in clustered Socket.IO deployments, causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-102600/"}