Is devise_invitable 2.0 vulnerable?

RubyGems · 15 releases from 2.0.0 to 2.0.14 · latest devise_invitable is 3.1.0 · checked 18 Nov 2026

No known advisories in the last release

devise_invitable 2.0.14, the last 2.0 release, has no known advisories. 1 advisory affects earlier 2.0.x releases, so update to 2.0.14.

Update within 2.0:bundle update --conservative devise_invitable # Gemfile: '>= 2.0.14'

Is your project on an affected devise_invitable?

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

  • MediumCVE-2023-48220GHSA-w3q8-m492-4pwp20 Feb 2024

    Possibility to circumvent the invitation token expiry period

    Affected
    >=0.4.rc3 <2.0.9
    Fixed in
    2.0.9

Every devise_invitable 2.0.x release

Affected: 2.0.0 to 2.0.8. 2.0.9 and later are not affected. Latest devise_invitable: 3.1.0.

VersionKnown advisories
devise_invitable 2.0.14None
devise_invitable 2.0.13None
devise_invitable 2.0.12None
devise_invitable 2.0.11None
devise_invitable 2.0.10None
devise_invitable 2.0.9None
devise_invitable 2.0.8CVE-2023-48220
devise_invitable 2.0.7CVE-2023-48220
devise_invitable 2.0.6CVE-2023-48220
devise_invitable 2.0.5CVE-2023-48220
devise_invitable 2.0.4CVE-2023-48220
devise_invitable 2.0.3CVE-2023-48220
devise_invitable 2.0.2CVE-2023-48220
devise_invitable 2.0.1CVE-2023-48220
devise_invitable 2.0.0CVE-2023-48220

Which of your client projects are still on devise_invitable 2.0?

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

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