Is guard-livereload 2.5 vulnerable?

RubyGems · 3 releases from 2.5.0 to 2.5.2 · latest guard-livereload is 2.5.2 · checked 18 Nov 2026

No known advisories in the last release

guard-livereload 2.5.2, the last 2.5 release, has no known advisories. 1 advisory affects earlier 2.5.x releases, so update to 2.5.2.

Update within 2.5: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

Fixed within 2.5.x, affecting earlier releases

  • 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.5.x release

Affected: 2.5.0 to 2.5.1. 2.5.2 is not affected.

VersionKnown advisories
guard-livereload 2.5.2None
guard-livereload 2.5.1CVE-2016-1000305
guard-livereload 2.5.0CVE-2016-1000305

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

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.