Is devise_token_auth 0.1 vulnerable?
RubyGems · 40 releases from 0.1.1 to 0.1.43 · latest devise_token_auth is 1.3.0 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. devise_token_auth 0.1.43, the last 0.1 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 0.1.43
Devise Token Auth vulnerable to Cross-site Scripting
- Affected
- >=0.1.33 <1.1.3
- Fixed in
- 1.1.3
Every devise_token_auth 0.1.x release
Affected: 0.1.33 to 0.1.43. Latest devise_token_auth: 1.3.0.
| Version | Known advisories |
|---|---|
| devise_token_auth 0.1.43 | CVE-2019-16751 |
| devise_token_auth 0.1.42 | CVE-2019-16751 |
| devise_token_auth 0.1.41 | CVE-2019-16751 |
| devise_token_auth 0.1.40 | CVE-2019-16751 |
| devise_token_auth 0.1.39 | CVE-2019-16751 |
| devise_token_auth 0.1.38 | CVE-2019-16751 |
| devise_token_auth 0.1.37 | CVE-2019-16751 |
| devise_token_auth 0.1.36 | CVE-2019-16751 |
| devise_token_auth 0.1.35 | CVE-2019-16751 |
| devise_token_auth 0.1.34 | CVE-2019-16751 |
| devise_token_auth 0.1.33 | CVE-2019-16751 |
| devise_token_auth 0.1.32 | None |
| devise_token_auth 0.1.31 | None |
| devise_token_auth 0.1.30 | None |
| devise_token_auth 0.1.29 | None |
| devise_token_auth 0.1.28 | None |
| devise_token_auth 0.1.27 | None |
| devise_token_auth 0.1.26 | None |
| devise_token_auth 0.1.25 | None |
| devise_token_auth 0.1.24 | None |
| devise_token_auth 0.1.23 | None |
| devise_token_auth 0.1.20 | None |
| devise_token_auth 0.1.18 | None |
| devise_token_auth 0.1.17 | None |
| devise_token_auth 0.1.16 | None |
| devise_token_auth 0.1.15 | None |
| devise_token_auth 0.1.14 | None |
| devise_token_auth 0.1.13 | None |
| devise_token_auth 0.1.12 | None |
| devise_token_auth 0.1.11 | None |
| devise_token_auth 0.1.10 | None |
| devise_token_auth 0.1.9 | None |
| devise_token_auth 0.1.8 | None |
| devise_token_auth 0.1.7 | None |
| devise_token_auth 0.1.6 | None |
| devise_token_auth 0.1.5 | None |
| devise_token_auth 0.1.4 | None |
| devise_token_auth 0.1.3 | None |
| devise_token_auth 0.1.2 | None |
| devise_token_auth 0.1.1 | None |
Which of your client projects are still on devise_token_auth 0.1?
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.