Is devise_token_auth 1.1 vulnerable?

RubyGems · 6 releases from 1.1.0 to 1.1.5 · latest devise_token_auth is 1.3.0 · checked 18 Nov 2026

No known advisories in the last release

devise_token_auth 1.1.5, the last 1.1 release, has no known advisories. 1 advisory affects earlier 1.1.x releases, so update to 1.1.5.

Update within 1.1:bundle update --conservative devise_token_auth # Gemfile: '>= 1.1.5'

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

Fixed within 1.1.x, affecting earlier releases

  • 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

Every devise_token_auth 1.1.x release

Affected: 1.1.0 to 1.1.2. 1.1.3 and later are not affected. Latest devise_token_auth: 1.3.0.

VersionKnown advisories
devise_token_auth 1.1.5None
devise_token_auth 1.1.4None
devise_token_auth 1.1.3None
devise_token_auth 1.1.2CVE-2019-16751
devise_token_auth 1.1.1CVE-2019-16751
devise_token_auth 1.1.0CVE-2019-16751

Which of your client projects are still on devise_token_auth 1.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.