Is rack-protection 1.0 vulnerable?

RubyGems · 1 release from 1.0.0 to 1.0.0 · latest rack-protection is 4.2.2 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. rack-protection 1.0.0, the last 1.0 release, is affected by 1 known security advisory (1 medium), including CVE-2018-1000119. Upgrade to 1.5.5 or later to fix all of them.

Upgrade with:bundle update --conservative rack-protection # Gemfile: '>= 1.5.5'

Is your project on an affected rack-protection?

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 rack-protection 1.0.0

  • MediumCVE-2018-1000119GHSA-688c-3x49-6rqj7 Mar 2018

    rack-protection gem timing attack vulnerability when validating CSRF token

    Affected
    <1.5.5 · >=2.0.0.beta1 <2.0.0
    Fixed in
    1.5.5, 2.0.0

Which of your client projects are still on rack-protection 1.0?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact rack-protection version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other rack-protection 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.