{"answers":{"affected":"2 open source packages ship an affected version, including websocket-driver.","exploited":"There is no known exploitation of CVE-2026-54464 in the wild and no public exploit code.","fix":"Upgrade websocket-driver to 0.8.1 or later.","what":"CVE-2026-54464 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-54464 and fix it if it is affected.\n\nWhat it is: CVE-2026-54464 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-54464 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-54464/ (Markdown: https://insights.sbomify.com/CVE-2026-54464/index.md)","id":"CVE-2026-54464","markdown":"https://insights.sbomify.com/CVE-2026-54464/index.md","name":"CVE-2026-54464","record":{"aliases":["DEBIAN-CVE-2026-54464","GHSA-33ph-fccm-39pj","MINI-6mvc-ggj8-2gj6","MINI-jmrm-8jmw-jgjq","UBUNTU-CVE-2026-54464"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Ruby WebSocket library","requires_auth":"none","summary":"Attackers can bypass message size limits in websocket-driver when using permessage-deflate, causing resource 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":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":"### Impact\n\nIf this library is used in tandem with the `permessage-deflate` extension, a\nWebSocket server or client can be made to accept messages that are larger than\nthe configured maximum message size. This is because this limit is checked\nagainst the message frames' length headers, which give the size of the\ncompressed data, not the size after decompression. This can lead to applications\naccepting larger messages than expected and exceeding their intended resource\nusage.\n\n### Patches\n\nThe issue has been patched in version 0.8.1, by checking the length of messages\nafter they are processed by incoming extensions. All users should upgrade to\nthis version.\n\n### Workarounds\n\nNo known workarounds exist.\n\n### Acknowledgements\n\nThis issue was discovered and reported by Pranjali Thakur, DepthFirst Security\nResearch Team.","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: Resource limit bypass via message compression","id":"CVE-2026-54464","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: Memory exhaustion in HTTP header parser","id":"CVE-2026-54465"},"packages":[{"ecosystem":"RubyGems","fixed":["0.8.1"],"introduced":["0"],"last_affected":[],"package":"websocket-driver","purl":null,"source":"GHSA-33ph-fccm-39pj"},{"ecosystem":"RubyGems","fixed":["0.8.1"],"introduced":["0"],"last_affected":[],"package":"websocket-driver","purl":"pkg:gem/websocket-driver","source":"GHSA-33ph-fccm-39pj"}],"prev":{"headline":"websocket-driver: Memory exhaustion via abuse of protocol length headers","id":"CVE-2026-54463"},"products":["websocket-driver-ruby"],"published":"2026-07-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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-21","vendors":["faye"]},"summary":"Attackers can bypass message size limits in websocket-driver when using permessage-deflate, causing resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-54464/"}