{"answers":{"affected":"2 open source packages ship an affected version, including websocket-driver. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-54466 in the wild and no public exploit code.","fix":"Upgrade websocket-driver to 0.7.5 or later.","what":"CVE-2026-54466 is a critical denial of service vulnerability in faye websocket-driver-node, published on 17 Jul 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-54466 and fix it if it is affected.\n\nWhat it is: CVE-2026-54466 is a critical denial of service vulnerability in faye websocket-driver-node, published on 17 Jul 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-54466 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- websocket-driver (npm): affected all versions; fixed in 0.7.5\n- websocket-driver (npm): affected all versions; fixed in 0.7.5\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-54466/ (Markdown: https://insights.sbomify.com/CVE-2026-54466/index.md)","id":"CVE-2026-54466","markdown":"https://insights.sbomify.com/CVE-2026-54466/index.md","name":"CVE-2026-54466","record":{"aliases":["CLEANSTART-2026-BN70978","CLEANSTART-2026-MI43337","CLEANSTART-2026-SA59159","DEBIAN-CVE-2026-54466","GHSA-xv26-6w52-cph6","MINI-343j-83v7-w4rf","MINI-4pvg-hp8j-62hg","MINI-576x-mghc-vwvv","MINI-5jh7-x63f-mrmx","MINI-7r67-mqjh-rg2j","MINI-83ww-5qpc-mhfv","MINI-c29r-pqp8-rp99","MINI-c9jm-3c57-66c4","OESA-2026-3212","ROOT-APP-NPM-CVE-2026-54466","UBUNTU-CVE-2026-54466"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js WebSocket library","requires_auth":"none","summary":"An attacker can cause message corruption and potential service disruption by sending malformed WebSocket frames with excessively large length headers.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"websocket-driver","vendor":"faye"}],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-130","name":"Improper Handling of Length Parameter Inconsistency"}],"description":"websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.7.5, the frame format in draft versions of the WebSocket protocol includes a length header that allows an arbitrarily large integer to be encoded as a sequence of bytes with the high bit set. By sending an indefinite sequence of bytes with values 0x80 or above, a client can make the server parse these bytes into an ever-growing integer in lib/websocket/driver/draft75.js; because JavaScript numbers are 64-bit floating point values, this number will eventually lose precision and lead to the subsequent payload being parsed incorrectly. This issue is fixed in version 0.7.5.","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":"websocket-driver: Message corruption via abuse of protocol length headers","id":"CVE-2026-54466","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Missing authorization in Trusted Firmware-M","id":"CVE-2026-54467"},"packages":[{"ecosystem":"npm","fixed":["0.7.5"],"introduced":["0"],"last_affected":[],"package":"websocket-driver","purl":null,"source":"GHSA-xv26-6w52-cph6"},{"ecosystem":"npm","fixed":["0.7.5"],"introduced":["0"],"last_affected":[],"package":"websocket-driver","purl":"pkg:npm/websocket-driver","source":"GHSA-xv26-6w52-cph6"}],"prev":{"headline":"websocket-driver: Memory exhaustion in HTTP header parser","id":"CVE-2026-54465"},"products":["websocket-driver-node"],"published":"2026-07-17","related":[{"cvss_score":6.9,"headline":"websocket-driver: Memory exhaustion via abuse of protocol length headers","id":"CVE-2026-54463","kev_date_added":null,"published":"2026-07-17"},{"cvss_score":6.3,"headline":"websocket-driver: Memory exhaustion in HTTP header parser","id":"CVE-2026-54465","kev_date_added":null,"published":"2026-07-17"}],"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":"US public information, NVD API terms","name":"NVD"},{"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-07-20","vendors":["faye"]},"summary":"An attacker can cause message corruption and potential service disruption by sending malformed WebSocket frames with excessively large length headers.","url":"https://insights.sbomify.com/CVE-2026-54466/"}