{"answers":{"affected":"2 open source packages ship an affected version, including engine.io.","exploited":"There is no known exploitation of CVE-2026-102599 in the wild and no public exploit code.","fix":"Upgrade engine.io to 6.6.10 or later.","what":"CVE-2026-102599 is a high-severity denial of service vulnerability in socketio socket.io, published on 13 Oct 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-102599 and fix it if it is affected.\n\nWhat it is: CVE-2026-102599 is a high-severity denial of service vulnerability in socketio socket.io, published on 13 Oct 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-102599 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- engine.io (npm): affected from 6.6.0; fixed in 6.6.10\n- engine.io (npm): affected from 6.6.0; fixed in 6.6.10\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-102599/ (Markdown: https://insights.sbomify.com/CVE-2026-102599/index.md)","id":"CVE-2026-102599","markdown":"https://insights.sbomify.com/CVE-2026-102599/index.md","name":"CVE-2026-102599","record":{"aliases":["GHSA-2gc4-cqfq-p2gv","MINI-x3vm-2xqf-rm69"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Socket.IO library","requires_auth":"none","summary":"A malicious client can cause a Node.js process crash via a crafted Engine.IO protocol revision mismatch during transport upgrade.","user_interaction":"not_required","vuln_class":"denial_of_service"},"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-248","name":"Uncaught Exception"}],"description":"Socket.IO enables bidirectional and low-latency communication for every platform. From Engine.IO 6.6.0 until 6.6.10, a transport upgrade can independently derive an Engine.IO protocol revision from the upgrade request instead of enforcing the revision stored on the existing session. A malicious client can establish a valid session and send an upgrade request with a different or omitted EIO query parameter, attaching a transport with incompatible parser and heartbeat behavior. A crafted heartbeat packet can then trigger an uncaught exception and terminate the Node.js process, including when Engine.IO v3 compatibility is disabled because an omitted EIO value is interpreted as revision 3 on the affected path. This issue is fixed in Engine.IO 6.6.10.","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: Engine.IO Protocol Revision Mismatch DoS","id":"CVE-2026-102599","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":"Socket.IO: Prototype Pollution via Unsafe Client Session Lookup","id":"CVE-2026-102600"},"packages":[{"ecosystem":"npm","fixed":["6.6.10"],"introduced":["6.6.0"],"last_affected":[],"package":"engine.io","purl":null,"source":"GHSA-2gc4-cqfq-p2gv"},{"ecosystem":"npm","fixed":["6.6.10"],"introduced":["6.6.0"],"last_affected":[],"package":"engine.io","purl":"pkg:npm/engine.io","source":"GHSA-2gc4-cqfq-p2gv"}],"prev":{"headline":"Werkzeug safe_join() allows Windows special device names","id":"CVE-2026-102598"},"products":["socket.io"],"published":"2026-10-13","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-10-17","vendors":["socketio"]},"summary":"A malicious client can cause a Node.js process crash via a crafted Engine.IO protocol revision mismatch during transport upgrade.","url":"https://insights.sbomify.com/CVE-2026-102599/"}