Is guard-livereload 2.1 vulnerable?

RubyGems · 4 releases from 2.1.0 to 2.1.3 · latest guard-livereload is 2.5.2 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. guard-livereload 2.1.3, the last 2.1 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.

Upgrade with:bundle update --conservative guard-livereload # Gemfile: '>= 2.5.2'

Is your project on an affected guard-livereload?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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.1.3

  • MediumCVE-2016-1000305GHSA-g65v-27r3-5p6m31 Jul 2026

    guard-livereload has a directory traversal vulnerability

    Affected
    <2.5.2
    Fixed in
    2.5.2

Every guard-livereload 2.1.x release

Affected: 2.1.0 to 2.1.3. Latest guard-livereload: 2.5.2.

VersionKnown advisories
guard-livereload 2.1.3CVE-2016-1000305
guard-livereload 2.1.2CVE-2016-1000305
guard-livereload 2.1.1CVE-2016-1000305
guard-livereload 2.1.0CVE-2016-1000305

Which of your client projects are still on guard-livereload 2.1?

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.