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.

Update within 3.1:bundle update --conservative bcrypt # Gemfile: '>= 3.1.22'

Is your project on an affected bcrypt?

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

  • MediumCVE-2026-33306GHSA-f27w-vcwj-c95419 Mar 2026

    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.

VersionKnown advisories
bcrypt 3.1.22None
bcrypt 3.1.21CVE-2026-33306
bcrypt 3.1.20CVE-2026-33306
bcrypt 3.1.19CVE-2026-33306
bcrypt 3.1.18CVE-2026-33306
bcrypt 3.1.17CVE-2026-33306
bcrypt 3.1.16CVE-2026-33306
bcrypt 3.1.15CVE-2026-33306
bcrypt 3.1.14CVE-2026-33306
bcrypt 3.1.13CVE-2026-33306
bcrypt 3.1.12CVE-2026-33306
bcrypt 3.1.11CVE-2026-33306
bcrypt 3.1.10CVE-2026-33306
bcrypt 3.1.9CVE-2026-33306
bcrypt 3.1.8CVE-2026-33306
bcrypt 3.1.7CVE-2026-33306
bcrypt 3.1.6CVE-2026-33306
bcrypt 3.1.3CVE-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.