Is guard-livereload 2.0 vulnerable?
RubyGems · 2 releases from 2.0.0 to 2.0.1 · latest guard-livereload is 2.5.2 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. guard-livereload 2.0.1, the last 2.0 release, is affected by 1 known security advisory (1 medium), including CVE-2016-1000305. Upgrade to 2.5.2 or later to fix all of them.
bundle update --conservative guard-livereload # Gemfile: '>= 2.5.2'Is your project on an affected guard-livereload?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting guard-livereload 2.0.1
guard-livereload has a directory traversal vulnerability
- Affected
- <2.5.2
- Fixed in
- 2.5.2
Every guard-livereload 2.0.x release
Affected: 2.0.0 to 2.0.1. Latest guard-livereload: 2.5.2.
| Version | Known advisories |
|---|---|
| guard-livereload 2.0.1 | CVE-2016-1000305 |
| guard-livereload 2.0.0 | CVE-2016-1000305 |
Which of your client projects are still on guard-livereload 2.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact guard-livereload version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other guard-livereload 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.