Is websocket-driver 0.8 vulnerable?
RubyGems · 3 releases from 0.8.0 to 0.8.2 · latest websocket-driver is 0.9.0 · checked 18 Nov 2026
No known advisories in the last release
websocket-driver 0.8.2, the last 0.8 release, has no known advisories. 4 advisories affect earlier 0.8.x releases, so update to 0.8.2.
bundle update --conservative websocket-driver # Gemfile: '>= 0.8.2'Is your project on an affected websocket-driver?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 0.8.x, affecting earlier releases
websocket-driver-ruby: Denial of service via malformed Host header
- Affected
- <0.8.2
- Fixed in
- 0.8.2
websocket-driver: Memory exhaustion in HTTP header parser
- Affected
- <0.8.1
- Fixed in
- 0.8.1
websocket-driver: Resource limit bypass via message compression
- Affected
- <0.8.1
- Fixed in
- 0.8.1
websocket-driver: Memory exhaustion via abuse of protocol length headers
- Affected
- <0.8.1
- Fixed in
- 0.8.1
Every websocket-driver 0.8.x release
Affected: 0.8.0 to 0.8.1. 0.8.2 is not affected. Latest websocket-driver: 0.9.0.
| Version | Known advisories |
|---|---|
| websocket-driver 0.8.2 | None |
| websocket-driver 0.8.1 | CVE-2026-61666 |
| websocket-driver 0.8.0 | CVE-2026-61666, CVE-2026-54465, CVE-2026-54464, CVE-2026-54463 |
Which of your client projects are still on websocket-driver 0.8?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact websocket-driver version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other websocket-driver versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the RubyGems registry. Refreshed daily.