Is devise_token_auth 0.2 vulnerable?

RubyGems · 1 release from 0.2.0 to 0.2.0 · latest devise_token_auth is 1.3.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. devise_token_auth 0.2.0, the last 0.2 release, is affected by 1 known security advisory (1 medium), including CVE-2019-16751. Upgrade to 1.1.3 or later to fix all of them.

Upgrade with:bundle update --conservative devise_token_auth # Gemfile: '>= 1.1.3'

Is your project on an affected devise_token_auth?

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 devise_token_auth 0.2.0

  • MediumCVE-2019-16751GHSA-mvqr-r76c-wm5f24 May 2022

    Devise Token Auth vulnerable to Cross-site Scripting

    Affected
    >=0.1.33 <1.1.3
    Fixed in
    1.1.3

Which of your client projects are still on devise_token_auth 0.2?

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

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