Is bcrypt 3.1 vulnerable?
RubyGems · 18 releases from 3.1.3 to 3.1.22 · latest bcrypt is 3.1.22 · checked 18 Nov 2026
No known advisories in the last release
bcrypt 3.1.22, the last 3.1 release, has no known advisories. 1 advisory affects earlier 3.1.x releases, so update to 3.1.22.
bundle update --conservative bcrypt # Gemfile: '>= 3.1.22'Is your project on an affected bcrypt?
Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 3.1.x, affecting earlier releases
bcrypt-ruby has an Integer Overflow that Causes Zero Key-Strengthening Iterations at Cost=31 on JRuby
- Affected
- <3.1.22
- Fixed in
- 3.1.22
Every bcrypt 3.1.x release
Affected: 3.1.3 to 3.1.21. 3.1.22 is not affected.
| Version | Known advisories |
|---|---|
| bcrypt 3.1.22 | None |
| bcrypt 3.1.21 | CVE-2026-33306 |
| bcrypt 3.1.20 | CVE-2026-33306 |
| bcrypt 3.1.19 | CVE-2026-33306 |
| bcrypt 3.1.18 | CVE-2026-33306 |
| bcrypt 3.1.17 | CVE-2026-33306 |
| bcrypt 3.1.16 | CVE-2026-33306 |
| bcrypt 3.1.15 | CVE-2026-33306 |
| bcrypt 3.1.14 | CVE-2026-33306 |
| bcrypt 3.1.13 | CVE-2026-33306 |
| bcrypt 3.1.12 | CVE-2026-33306 |
| bcrypt 3.1.11 | CVE-2026-33306 |
| bcrypt 3.1.10 | CVE-2026-33306 |
| bcrypt 3.1.9 | CVE-2026-33306 |
| bcrypt 3.1.8 | CVE-2026-33306 |
| bcrypt 3.1.7 | CVE-2026-33306 |
| bcrypt 3.1.6 | CVE-2026-33306 |
| bcrypt 3.1.3 | CVE-2026-33306 |
Which of your client projects are still on bcrypt 3.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact bcrypt version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
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.