Vulnerabilities

Vulnerability · CVE-2026-33306

bcrypt-ruby is a Ruby binding for the OpenBSD bcrypt() password hashing algorithm.

Published Mar 24, 2026 · catalog updated Jun 17, 2026 · bcrypt-ruby project

Check if you run it

No confirmed exploitation is on record for CVE-2026-33306. EPSS is 0.26%. Act only if a listed version of bcrypt-ruby project is installed.

Gaps on this record

  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.26%
Remediation
Advisory link
Affected products
cpe bcrypt-ruby project/bcrypt-ruby

bcrypt-ruby is a Ruby binding for the OpenBSD bcrypt() password hashing algorithm. Prior to version 3.1.22, an integer overflow in the Java BCrypt implementation for JRuby can cause zero iterations in the strengthening loop. Impacted applications must be setting the cost to 31 to see this happen. The JRuby implementation of bcrypt-ruby ( ) computes the key-strengthening round count as a signed 32-bit integer. When (the maximum allowed by the gem), signed integer overflow causes the round count to become negative, and the strengthening loop executes **zero iterations**. This collapses bcrypt from 2^31 rounds of exponential key-strengthening to effectively constant-time computation — only the initial EksBlowfish key setup and final 64x encryption phase remain. The resulting hash looks valid ( ) and verifies correctly via , making the weakness invisible to the application. This issue is triggered only when cost=31 is used or when verifying a hash. This problem has been fixed in version 3.1.22. As a workaround, set the cost to something less than 31.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe bcrypt-ruby project/bcrypt-rubyversion unspecified

How to fix CVE-2026-33306

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-33306. EPSS is 0.26%. Act only if a listed version of bcrypt-ruby project is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-190: Integer Overflow. EPSS 0.26%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 24, 2026 · NIST NVD

    Detected

    bcrypt-ruby is a Ruby binding for the OpenBSD bcrypt() password hashing algorithm. Prior to version 3.1.22, an integer overflow in the Java BCrypt implementation for JRuby can cause zero iterations in the strengthening loop. Impacted applications must be setting the cost to 31 to see this happen. The JRuby implementation of bcrypt-ruby ( ) computes the key-strengthening round count as a signed 32-

  2. Jun 17, 2026 · NIST NVD

    Updated

    bcrypt-ruby is a Ruby binding for the OpenBSD bcrypt() password hashing algorithm. Prior to version 3.1.22, an integer overflow in the Java BCrypt implementation for JRuby can cause zero iterations in the strengthening loop. Impacted applications must be setting the cost to 31 to see this happen. The JRuby implementation of bcrypt-ruby ( ) computes the key-strengthening round count as a signed 32-

Sources

  • CVE.orgVulnerability recordCVE-2026-33306

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-33306

    30-day exploitation probability 0.3%

    first.org
  • NIST NVDVulnerability recordCVE-2026-33306

    bcrypt-ruby is a Ruby binding for the OpenBSD bcrypt() password hashing algorithm. Prior to version 3.1.22, an integer overflow in the Java BCrypt implementation for JRuby can cause zero iterations in the strengthening loop. Impacted applications must be setting the cost to 31 t

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.