Is devise 5.0 vulnerable?

RubyGems · 5 releases from 5.0.0 to 5.0.4 · latest devise is 5.0.4 · checked 18 Nov 2026

No known advisories in the last release

devise 5.0.4, the last 5.0 release, has no known advisories. 2 advisories affect earlier 5.0.x releases, so update to 5.0.4.

Update within 5.0:bundle update --conservative devise # Gemfile: '>= 5.0.4'

Is your project on an affected devise?

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 5.0.x, affecting earlier releases

  • MediumCVE-2026-40295GHSA-jp94-3292-c3xv8 May 2026

    Devise has an Open Redirect via Unvalidated `request.referrer` in Timeoutable Session Timeout Handler

    Affected
    <5.0.4
    Fixed in
    5.0.4
  • MediumCVE-2026-32700GHSA-57hq-95w6-v4fc17 Mar 2026

    Devise has a confirmable "change email" race condition permits user to confirm email they have no access to

    Affected
    <5.0.3
    Fixed in
    5.0.3

Every devise 5.0.x release

Affected: 5.0.0 to 5.0.3. 5.0.4 is not affected.

VersionKnown advisories
devise 5.0.4None
devise 5.0.3CVE-2026-40295
devise 5.0.2CVE-2026-40295, CVE-2026-32700
devise 5.0.1CVE-2026-40295, CVE-2026-32700
devise 5.0.0CVE-2026-40295, CVE-2026-32700

Which of your client projects are still on devise 5.0?

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

Other devise 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.