Is devise_token_auth 1.0 vulnerable?
RubyGems · 1 release from 1.0.0 to 1.0.0 · latest devise_token_auth is 1.3.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. devise_token_auth 1.0.0, the last 1.0 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.
bundle update --conservative devise_token_auth # Gemfile: '>= 1.1.3'Is your project on an affected devise_token_auth?
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 1.0.0
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 1.0?
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.