Vulnerability Database · RubyGems · devise · Version
devise 4.0.0
4.0.0 is affected by 4 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 5.0.4.
Critical 0 High 0 Medium 4 Low 0 Unrated 0
-
Released 18 Apr 2016
Licence MIT
Also known from other sources 4
Newer releases 173
Database updated 23/Oct/2026
Release and licence data published by RubyGems. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
devise 4.0.0 vulnerabilities
4 vulnerabilities cover devise 4.0.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-40295: Devise Open Redirect Vulnerability in Timeoutable Session Timeout Handler | 6.1 medium | 5.0.4 | 08 May 2026 |
| CVE-2026-32700: Devise Email Change Race Condition Vulnerability | 6.0 medium | 5.0.3 | 17 Mar 2026 |
| CVE-2019-16109: Authentication Bypass in Devise | 5.3 medium | 4.7.1 | 11 Sep 2019 |
| CVE-2019-5421: Time-of-check Time-of-use Race Condition in devise Ruby Gem | N/A medium | 4.6.0 | 19 Mar 2019 |
Looking for another version, or everything Vulert holds for devise?
Questions
About devise 4.0.0
Is devise 4.0.0 vulnerable?
Yes. 4 vulnerabilities in the Vulert database cover devise 4.0.0: 0 critical, 0 high, 4 medium and 0 low. The upgrade Vulert recommends is 5.0.4, and each entry above names the fixed version to move to.
Which version of devise should I use instead of 4.0.0?
5.0.4 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 4.0.0 the latest release of devise?
No. 4.0.0 was published 18 Apr 2016, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor devise for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the devise version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.