{"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-54465 in the wild and no public exploit code.","fix":"Upgrade websocket-driver to 0.8.1 or later.","what":"CVE-2026-54465 is a medium-severity denial of service vulnerability in faye websocket-driver-ruby, 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-54465 and fix it if it is affected.\n\nWhat it is: CVE-2026-54465 is a medium-severity denial of service vulnerability in faye websocket-driver-ruby, 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-54465 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- websocket-driver (RubyGems): affected all versions; fixed in 0.8.1\n- websocket-driver (RubyGems): affected all versions; fixed in 0.8.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-54465/ (Markdown: https://insights.sbomify.com/CVE-2026-54465/index.md)","id":"CVE-2026-54465","markdown":"https://insights.sbomify.com/CVE-2026-54465/index.md","name":"CVE-2026-54465","record":{"aliases":["CLSA-2026-1790944051","DEBIAN-CVE-2026-54465","GHSA-8j3g-f24p-4mpw","MINI-fw6f-crwq-545w","MINI-jrjr-cc7r-pvxc","UBUNTU-CVE-2026-54465"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Ruby WebSocket library","requires_auth":"none","summary":"A remote attacker can cause memory exhaustion and denial of service in applications using the websocket-driver library by sending excessive HTTP 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":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"websocket-driver is a WebSocket protocol handler with pluggable I/O. Prior to 0.8.1, when websocket-driver is used to implement a WebSocket server on top of a TCP server using WebSocket::Driver.server() or to complement a WebSocket client, a peer can make a single connection consume an unbounded amount of memory by sending an HTTP request or response with a never-ending list of headers. This can lead to the receiving process running out of memory. This issue is fixed in version 0.8.1.","ecosystems":["RubyGems"],"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: Memory exhaustion in HTTP header parser","id":"CVE-2026-54465","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"websocket-driver: Message corruption via abuse of protocol length headers","id":"CVE-2026-54466"},"packages":[{"ecosystem":"RubyGems","fixed":["0.8.1"],"introduced":["0"],"last_affected":[],"package":"websocket-driver","purl":null,"source":"GHSA-8j3g-f24p-4mpw"},{"ecosystem":"RubyGems","fixed":["0.8.1"],"introduced":["0"],"last_affected":[],"package":"websocket-driver","purl":"pkg:gem/websocket-driver","source":"GHSA-8j3g-f24p-4mpw"}],"prev":{"headline":"websocket-driver: Resource limit bypass via message compression","id":"CVE-2026-54464"},"products":["websocket-driver-ruby"],"published":"2026-07-17","related":[{"cvss_score":9.2,"headline":"websocket-driver: Message corruption via abuse of protocol length headers","id":"CVE-2026-54466","kev_date_added":null,"published":"2026-07-17"},{"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"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-20","vendors":["faye"]},"summary":"A remote attacker can cause memory exhaustion and denial of service in applications using the websocket-driver library by sending excessive HTTP headers.","url":"https://insights.sbomify.com/CVE-2026-54465/"}