Is websocket-extensions 0.1 vulnerable?
RubyGems · 6 releases from 0.1.0 to 0.1.5 · latest websocket-extensions is 0.2.0 · checked 18 Nov 2026
No known advisories in the last release
websocket-extensions 0.1.5, the last 0.1 release, has no known advisories. 1 advisory affects earlier 0.1.x releases, so update to 0.1.5.
bundle update --conservative websocket-extensions # Gemfile: '>= 0.1.5'Is your project on an affected websocket-extensions?
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.1.x, affecting earlier releases
Regular Expression Denial of Service in websocket-extensions (RubyGem)
- Affected
- <0.1.5
- Fixed in
- 0.1.5
Every websocket-extensions 0.1.x release
Affected: 0.1.0 to 0.1.4. 0.1.5 is not affected. Latest websocket-extensions: 0.2.0.
| Version | Known advisories |
|---|---|
| websocket-extensions 0.1.5 | None |
| websocket-extensions 0.1.4 | CVE-2020-7663 |
| websocket-extensions 0.1.3 | CVE-2020-7663 |
| websocket-extensions 0.1.2 | CVE-2020-7663 |
| websocket-extensions 0.1.1 | CVE-2020-7663 |
| websocket-extensions 0.1.0 | CVE-2020-7663 |
Which of your client projects are still on websocket-extensions 0.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact websocket-extensions version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other websocket-extensions 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.